← previous blocknext block →recent activity
Analyzing
Block #84,364,511
13 transactions · 8 stateful · 2026-06-29 01:22:23 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,364,511 · 13 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
5w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e2262…cd8c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd6d4eb00…30f3
0x34b655…2a6f
4 touches
1 conflict
0x0c119c6d…a42e
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x4befd245…22fa
0x34b655…2a6f
2 touches
0 conflicts
0x93641233…06f5
0x34b655…2a6f
2 touches
0 conflicts
0x94a845e8…8e2a
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 0xfd4e22625a…b8cd8c
Audit this contract →
← previous block·next block →recent activity