← previous blocknext block →recent activity
Analyzing
Block #86,126,916
9 transactions · 8 stateful · 2026-07-07 05:11:44 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,126,916 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfce8a0c…c8c7
0x34b655…2a6f
4 touches
1 conflict
0xa8dbe7b0…8bad
0x34b655…2a6f
4 touches
1 conflict
0xadb0aec6…48ee
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x7fa509a2…3ec9
0x34b655…2a6f
2 touches
0 conflicts
0x9bf36d4e…1f3e
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 0xcfce8a0c00…82c8c7
Audit this contract →
← previous block·next block →recent activity