← previous blocknext block →recent activity
Analyzing
Block #84,564,157
13 transactions · 11 stateful · 2026-06-29 23:34:00 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,564,157 · 13 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
3w06w17w08w19w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd1b178b…a36c
0x34b655…2a6f
4 touches
1 conflict
0x8d0e1d29…cd3e
0x34b655…2a6f
4 touches
1 conflict
0xa42e8482…b88f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xacb691b6…8e39
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xed660153…a905
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
1 conflict on slot 0xfd1b178b13…a9a36c
Audit this contract →
← previous block·next block →recent activity