← previous blocknext block →recent activity
Analyzing
Block #86,664,675
13 transactions · 12 stateful · 2026-07-09 17:07:01 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,664,675 · 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
1w02w13w04w16w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb3be380…ed0e
0x34b655…2a6f
6 touches
3 conflicts
0x2c4fe59f…9592
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x33eb5dfa…2338
0x34b655…2a6f
4 touches
1 conflict
0x45918488…1f91
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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 0xbb3be38071…0bed0e
Audit this contract →
← previous block·next block →recent activity