← previous blocknext block →recent activity
Analyzing
Block #86,674,040
13 transactions · 9 stateful · 2026-07-09 18:09:32 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,674,040 · 13 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
2w05w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x015c6c43…fa58
0x34b655…2a6f
2 touches
0 conflicts
0x015df8f9…c874
0x34b655…2a6f
2 touches
0 conflicts
0x01df0928…3426
0x34b655…2a6f
2 touches
0 conflicts
0x0682a731…d1e7
0x34b655…2a6f
2 touches
0 conflicts
0x0b320394…cc69
0x34b655…2a6f
2 touches
0 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity