← previous blocknext block →recent activity
Analyzing
Block #83,904,374
14 transactions · 13 stateful · 2026-06-26 22:17:03 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,904,374 · 14 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
1w02w17w08w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfaba664…0898
0x34b655…2a6f
4 touches
1 conflict
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x1cc08c30…cd41
0x34b655…2a6f
4 touches
1 conflict
0x2173dcc9…63df
0x34b655…2a6f
4 touches
1 conflict
0xcd342fd8…4e95
0x96b79e…d00a
4 touches
1 conflict
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: Perpl
1 conflict on slot 0xdfaba66455…d10898
Audit this contract →
← previous block·next block →recent activity