← previous blocknext block →recent activity
Analyzing
Block #84,252,436
11 transactions · 10 stateful · 2026-06-28 12:55:32 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,252,436 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bd818fc…4f86
0x34b655…2a6f
6 touches
3 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
6 touches
3 conflicts
0x4e7b9499…462c
0x34b655…2a6f
4 touches
1 conflict
0x9b19dfc8…0d06
0x34b655…2a6f
4 touches
1 conflict
0xa8c03146…b71e
0x34b655…2a6f
4 touches
1 conflict
0xd026fe03…7748
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
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 0x5bd818fcf8…714f86
Audit this contract →
← previous block·next block →recent activity