← previous blocknext block →recent activity
Analyzing
Block #84,319,829
13 transactions · 11 stateful · 2026-06-28 20:24:31 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,319,829 · 13 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
4w06w07w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0x5df6102c…6494
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0xb088ddad…821d
0x11ed3b…2c96
2 touches
0 conflicts
0xcd621226…2df8
0x98dc6e…8633
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0003
0x2d59fc…cd50
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
3 conflicts on slot 0xe732567db9…26b65d
Audit this contract →
← previous block·next block →recent activity