← previous blocknext block →recent activity
Analyzing
Block #86,793,615
16 transactions · 13 stateful · 2026-07-10 07:28:00 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,793,615 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x0c93b85b…fe15
0x34b655…2a6f
4 touches
1 conflict
0x1ebe108b…72a0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2cf89f67…4f1b
0x34b655…2a6f
4 touches
1 conflict
0x2e6b89c0…e2d3
0x34b655…2a6f
4 touches
1 conflict
0x31488d63…18f4
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
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 0x06aed19eee…1cca57
Audit this contract →
← previous block·next block →recent activity