← previous blocknext block →recent activity
Analyzing
Block #105,933,329
22 transactions · 22 stateful · 2026-09-18 16:01:21 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,933,329 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w39w010w111w212w313w415w117w218w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049a66c3…1949
0x6f6493…b480
10 touches
10 conflicts
0x162f39bf…d831
0x6f6493…b480
10 touches
10 conflicts
0x17dba174…eb05
0x6f6493…b480
10 touches
10 conflicts
0xa86ddaa1…4b6e
0x6f6493…b480
10 touches
10 conflicts
0xbd851260…15e4
0x6f6493…b480
10 touches
10 conflicts
0xc287a00c…05d3
0x6f6493…b480
10 touches
10 conflicts
0xd39bee68…372f
0x6f6493…b480
10 touches
10 conflicts
0xd39bee68…3733
0x6f6493…b480
10 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x6f6493e3…08b480
10 conflicts on slot 0x049a66c38f…fb1949
Audit this contract →
← previous block·next block →recent activity