← previous blocknext block →recent activity
Analyzing
Block #84,535,969
20 transactions · 9 stateful · 2026-06-29 20:25:32 UTC
Parallelism
90/100
Blocked
22%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,535,969 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x39cc2185…cacb
0x34b655…2a6f
2 touches
0 conflicts
0x56a41786…3508
0x34b655…2a6f
2 touches
0 conflicts
0x71ab4d41…eea7
0x34b655…2a6f
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 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity