← previous blocknext block →recent activity
Analyzing
Block #86,320,130
15 transactions · 14 stateful · 2026-07-08 02:41:53 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,320,130 · 15 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
1w02w14w05w16w07w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18aed20c…48f3
0x000000…012a
6 touches
3 conflicts
0x00000000…0004
0xd5b70d…615b
6 touches
3 conflicts
0x7c403af1…31b1
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0000
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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: AUSD (AUSD)
3 conflicts on slot 0x18aed20c69…4f48f3
Audit this contract →
← previous block·next block →recent activity