← previous blocknext block →recent activity
Analyzing
Block #85,958,191
31 transactions · 19 stateful · 2026-07-06 10:25:18 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,958,191 · 31 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w012w015w117w224w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x4a76ba17…b1a9
0x065c9d…c394
3 touches
1 conflict
0x3b9a6da2…b935
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity