← previous blocknext block →recent activity
Analyzing
Block #84,526,483
15 transactions · 14 stateful · 2026-06-29 19:22:19 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,526,483 · 15 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
5w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99246de6…5bd5
0x34b655…2a6f
4 touches
1 conflict
0xd71cd8f7…be01
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8f2f9e67…3be0
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x162e5f03…ced2
0x34b655…2a6f
2 touches
0 conflicts
0x2eea2b1d…b2fa
0x34b655…2a6f
2 touches
0 conflicts
0x334b211a…dfd8
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 0x99246de64f…485bd5
Audit this contract →
← previous block·next block →recent activity