← previous blocknext block →recent activity
Analyzing
Block #86,104,777
13 transactions · 13 stateful · 2026-07-07 02:43:55 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,104,777 · 13 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c37629d…9e3f
0x34b655…2a6f
4 touches
1 conflict
0x83dea465…8a72
0x34b655…2a6f
4 touches
1 conflict
0x931619e4…3b17
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x5346d2b6…b717
0x065c9d…c394
2 touches
0 conflicts
0x8fbeab4a…80d7
0x065c9d…c394
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 0x7c37629d56…dd9e3f
Audit this contract →
← previous block·next block →recent activity