← previous blocknext block →recent activity
Analyzing
Block #85,891,864
18 transactions · 12 stateful · 2026-07-06 03:03:07 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,891,864 · 18 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
1w02w13w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0x2638dade…45af
0x34b655…2a6f
3 touches
1 conflict
0x81906a8e…9459
0x34b655…2a6f
3 touches
1 conflict
0xe2263bea…6a9d
0x69df8a…6292
2 touches
0 conflicts
0xe2263bea…6a9f
0x69df8a…6292
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 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity