← previous blocknext block →recent activity
Analyzing
Block #83,410,468
21 transactions · 17 stateful · 2026-06-24 15:21:15 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,410,468 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w08w110w211w312w413w519w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x757b0543…e087
0x34b655…2a6f
8 touches
6 conflicts
0x901d9f30…67a4
0x34b655…2a6f
8 touches
6 conflicts
0xec7b070f…db9a
0x34b655…2a6f
8 touches
6 conflicts
0xdb13034e…be94
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity