← previous blocknext block →recent activity
Analyzing
Block #84,365,251
23 transactions · 19 stateful · 2026-06-29 01:27:20 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,365,251 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w18w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x93641233…06f5
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x2f4d415d…5f95
0x34b655…2a6f
4 touches
1 conflict
0x8f0e8a2f…a850
0x34b655…2a6f
3 touches
1 conflict
0x11622504…ed25
0x754704…b603
2 touches
0 conflicts
0x74fa2096…56ea
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity