← previous blocknext block →recent activity
Analyzing
Block #84,364,407
10 transactions · 10 stateful · 2026-06-29 01:21:42 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,364,407 · 10 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
2w03w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f0e8a2f…a850
0x34b655…2a6f
4 touches
1 conflict
0xd8a49b87…5d96
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x247e4d3d…7313
0x065c9d…c394
2 touches
0 conflicts
0x3d56e968…7600
0x065c9d…c394
2 touches
0 conflicts
0x42b37053…d1f9
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
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: Perpl
1 conflict on slot 0x8f0e8a2f96…7ba850
Audit this contract →
← previous block·next block →recent activity