← previous blocknext block →recent activity
Analyzing
Block #84,495,335
21 transactions · 18 stateful · 2026-06-29 15:54:34 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,495,335 · 21 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
1w02w03w04w05w16w28w19w112w113w014w116w017w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x7ab8d4ad…14c3
0x34b655…2a6f
4 touches
1 conflict
0x7fa1794c…3323
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x92132ed7…2722
0x34b655…2a6f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity