← previous blocknext block →recent activity
Analyzing
Block #86,741,752
13 transactions · 11 stateful · 2026-07-10 01:41:41 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,741,752 · 13 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
1w02w14w05w17w28w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d05c2b3…bd7f
0x34b655…2a6f
6 touches
3 conflicts
0x5f14622f…73ee
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xdb6aaff6…d579
0x34b655…2a6f
6 touches
3 conflicts
0x0d05c2b3…bd7e
0x34b655…2a6f
6 touches
3 conflicts
0x93324a17…387b
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8912
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8913
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
3 conflicts on slot 0x0d05c2b379…c0bd7f
Audit this contract →
← previous block·next block →recent activity