← previous blocknext block →recent activity
Analyzing
Block #86,335,695
12 transactions · 11 stateful · 2026-07-08 04:25:49 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,335,695 · 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
1w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1b416b9…8810
0x065c9d…c394
3 touches
1 conflict
0xbe5595f2…bb4f
0x065c9d…c394
3 touches
1 conflict
0x1b429ceb…7210
0x065c9d…c394
2 touches
0 conflicts
0x57c96ade…b3ef
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
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 0x4bfdcd5135…769b58
Audit this contract →
← previous block·next block →recent activity