← previous blocknext block →recent activity
Analyzing
Block #85,926,989
14 transactions · 12 stateful · 2026-07-06 06:57:10 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,926,989 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w210w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x76409f96…0ca6
0x34b655…2a6f
6 touches
3 conflicts
0x141c490e…8343
0x34b655…2a6f
6 touches
3 conflicts
0xa966b790…877b
0x34b655…2a6f
6 touches
3 conflicts
0x1fdeff02…6d28
0x34b655…2a6f
6 touches
3 conflicts
0xfa870fe3…0642
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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