← previous blocknext block →recent activity
Analyzing
Block #84,491,196
11 transactions · 9 stateful · 2026-06-29 15:26:55 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,491,196 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x1728ed63…499c
0xea1b8e…c5ec
4 touches
1 conflict
0x4b18d9ab…5581
0x1efe02…37d6
2 touches
0 conflicts
0x628927fe…7f2c
0x1efe02…37d6
2 touches
0 conflicts
0x2a4dbc20…1421
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x7534f53d…6ed4
0x34b655…2a6f
2 touches
0 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: 0xd637b38f…c64160
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity