← previous blocknext block →recent activity
Analyzing
Block #86,305,026
12 transactions · 9 stateful · 2026-07-08 01:00:53 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,305,026 · 12 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd40bddc1…773c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x550fe940…e6d8
0x065c9d…c394
2 touches
0 conflicts
0x6341d6f1…d5b0
0x065c9d…c394
2 touches
0 conflicts
0x63bf1a61…32e3
0x065c9d…c394
2 touches
0 conflicts
0xb809c17b…c286
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xd40bddc144…4e773c
Audit this contract →
← previous block·next block →recent activity