← previous blocknext block →recent activity
Analyzing
Block #83,580,720
11 transactions · 11 stateful · 2026-06-25 10:17:11 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,580,720 · 11 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
1w02w14w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e1ce17e…98a7
0x34b655…2a6f
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x24d68cf2…09b7
0x34b655…2a6f
3 touches
1 conflict
0x73202e4b…16bb
0x065c9d…c394
2 touches
0 conflicts
0x795f3190…9639
0x065c9d…c394
2 touches
0 conflicts
0xbbafd4a4…cec8
0x065c9d…c394
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 0x4e1ce17e14…ed98a7
Audit this contract →
← previous block·next block →recent activity