← previous blocknext block →recent activity
Analyzing
Block #84,060,163
14 transactions · 13 stateful · 2026-06-27 15:35:01 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,060,163 · 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
12w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59ed335a…d2f3
0x34b655…2a6f
4 touches
1 conflict
0xa6c9a33e…d839
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xee9fe9a8…98d0
0x34b655…2a6f
4 touches
1 conflict
0x1b3f23da…7b77
0x34b655…2a6f
2 touches
0 conflicts
0x2328941c…84d3
0x34b655…2a6f
2 touches
0 conflicts
0x6051a0fb…e112
0x34b655…2a6f
2 touches
0 conflicts
0x63f848df…7824
0x34b655…2a6f
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 0x59ed335a81…67d2f3
Audit this contract →
← previous block·next block →recent activity