← previous blocknext block →recent activity
Analyzing
Block #86,384,494
31 transactions · 25 stateful · 2026-07-08 09:51:57 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,384,494 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w19w010w116w017w119w220w323w324w425w428w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
8 touches
6 conflicts
0x21d22421…0b7a
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xff0658e8…cba2
0x34b655…2a6f
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5847e4f7…1fd3
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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
6 conflicts on slot 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity