← previous blocknext block →recent activity
Analyzing
Block #85,625,028
14 transactions · 13 stateful · 2026-07-04 21:24:56 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,625,028 · 14 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
1w02w17w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd27d3461…72b1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x7e1faa73…bfbf
0x34b655…2a6f
4 touches
1 conflict
0xc0a4133e…6110
0x34b655…2a6f
4 touches
1 conflict
0x588fa18f…f0fd
0x40c49f…2af0
2 touches
0 conflicts
0x58d2b697…2b27
0x40c49f…2af0
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 0xd27d3461bf…ea72b1
Audit this contract →
← previous block·next block →recent activity