← previous blocknext block →recent activity
Analyzing
Block #86,851,908
16 transactions · 13 stateful · 2026-07-10 13:57:46 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,851,908 · 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
1w03w16w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x698e3c53…a4c4
0x34b655…2a6f
6 touches
3 conflicts
0xf722980d…ce99
0x34b655…2a6f
4 touches
1 conflict
0xf6971361…0e3e
0x34b655…2a6f
4 touches
1 conflict
0xbdb2111f…1402
0x34b655…2a6f
4 touches
1 conflict
0x98cc6884…3a83
0x34b655…2a6f
4 touches
1 conflict
0x9836123e…0e41
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
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 0x698e3c537a…0da4c4
Audit this contract →
← previous block·next block →recent activity