← previous blocknext block →recent activity
Analyzing
Block #86,817,056
18 transactions · 16 stateful · 2026-07-10 10:04:39 UTC
Parallelism
78/100
Blocked
19%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,817,056 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d52fb7…c165
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x1082298a…e05f
0x34b655…2a6f
4 touches
1 conflict
0xfee72f1e…0aee
0x34b655…2a6f
4 touches
1 conflict
0x1082298a…e05e
0x34b655…2a6f
4 touches
1 conflict
0x823a3658…acf6
0x34b655…2a6f
4 touches
1 conflict
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0xa05860b1…782e
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
6 conflicts on slot 0xa6d52fb75b…0ec165
Audit this contract →
← previous block·next block →recent activity