← previous blocknext block →recent activity
Analyzing
Block #86,047,409
14 transactions · 12 stateful · 2026-07-06 20:21:24 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,047,409 · 14 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
1w02w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63ce81c4…c889
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
0x34b655…2a6f
2 touches
0 conflicts
0x30fa662a…06e0
0x34b655…2a6f
2 touches
0 conflicts
0x32be4f5d…7901
0x34b655…2a6f
2 touches
0 conflicts
0x814de043…458c
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 0x63ce81c4dc…e6c889
Audit this contract →
← previous block·next block →recent activity