← previous blocknext block →recent activity
Analyzing
Block #84,491,863
16 transactions · 15 stateful · 2026-06-29 15:31:23 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,491,863 · 16 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
5w06w07w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5970b31…f34c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8fcf2308…746e
0x34b655…2a6f
4 touches
1 conflict
0x2492be03…22c9
0x34b655…2a6f
2 touches
0 conflicts
0x50c4e81e…ce2d
0x34b655…2a6f
2 touches
0 conflicts
0x62554ce4…109e
0x34b655…2a6f
2 touches
0 conflicts
0x721f5631…06ee
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 0xf5970b3144…10f34c
Audit this contract →
← previous block·next block →recent activity