← previous blocknext block →recent activity
Analyzing
Block #86,084,562
34 transactions · 25 stateful · 2026-07-07 00:29:01 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,084,562 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w121w023w024w127w028w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0xd77e90ec…8c04
0x3bd359…433a
6 touches
3 conflicts
0x01737532…9b12
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x97785d36…2ac5
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity