← previous blocknext block →recent activity
Analyzing
Block #84,360,320
17 transactions · 13 stateful · 2026-06-29 00:54:29 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,360,320 · 17 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
2w06w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x8fcf2308…746e
0x34b655…2a6f
4 touches
1 conflict
0x18c610ca…b213
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x4f002fe8…9b12
0x34b655…2a6f
2 touches
0 conflicts
0x5f3fc680…f989
0x34b655…2a6f
2 touches
0 conflicts
0x6d0ee0b3…0d36
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity