← previous blocknext block →recent activity
Analyzing
Block #86,793,678
14 transactions · 12 stateful · 2026-07-10 07:28:24 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,793,678 · 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
1w02w14w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xb96e477f…54e9
0x34b655…2a6f
4 touches
1 conflict
0xb96e477f…54e8
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7e
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7f
0x34b655…2a6f
4 touches
1 conflict
0xc6bb7e6c…bf35
0x34b655…2a6f
4 touches
1 conflict
0x2b3345cb…cb6b
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 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity