← previous blocknext block →recent activity
Analyzing
Block #84,282,576
14 transactions · 14 stateful · 2026-06-28 16:16:20 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,282,576 · 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
1w05w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0x05eab560…19e2
0x2ab50b…5c41
2 touches
0 conflicts
0x0991fdda…a745
0x2ab50b…5c41
2 touches
0 conflicts
0x0d3dde59…204f
0x2ab50b…5c41
2 touches
0 conflicts
0x0f6fafe4…9688
0x2ab50b…5c41
2 touches
0 conflicts
0x0f8178c8…0ab7
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity