← previous blocknext block →recent activity
Analyzing
Block #83,493,057
14 transactions · 13 stateful · 2026-06-25 00:32:36 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,493,057 · 14 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
2w03w15w06w17w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x084b86f8…4a63
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
6 touches
3 conflicts
0x040d237c…b53c
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x5d1d0ae6…b621
0x34b655…2a6f
4 touches
1 conflict
0x7527802e…2ba9
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
3 conflicts on slot 0x084b86f841…8d4a63
Audit this contract →
← previous block·next block →recent activity