← previous blocknext block →recent activity
Analyzing
Block #84,036,598
11 transactions · 9 stateful · 2026-06-27 12:57:55 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,036,598 · 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
5w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07f69062…03ec
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x756ad195…36a3
0x34b655…2a6f
6 touches
3 conflicts
0x2fbb25e7…87d3
0x34b655…2a6f
4 touches
1 conflict
0x33edefd2…bf4f
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x4c8b47b1…ea57
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
6 conflicts on slot 0x07f6906240…ea03ec
Audit this contract →
← previous block·next block →recent activity