← previous blocknext block →recent activity
Analyzing
Block #83,398,700
24 transactions · 20 stateful · 2026-06-24 14:02:34 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,398,700 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w18w29w310w411w512w614w222w323w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xaa6f28d9…83ef
0x34b655…2a6f
6 touches
3 conflicts
0x92f3f897…d0ec
0x34b655…2a6f
6 touches
3 conflicts
0x43b88c5d…02ac
0x34b655…2a6f
4 touches
1 conflict
0x5d2b5661…df66
0x34b655…2a6f
4 touches
1 conflict
0x86519d88…7dd2
0x34b655…2a6f
4 touches
1 conflict
0x9c7571b3…9605
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity