← previous blocknext block →recent activity
Analyzing
Block #86,697,346
17 transactions · 14 stateful · 2026-07-09 20:45:02 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,697,346 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w010w111w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9581b59…3c08
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21bf
0x1b6862…e19c
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 0xd9581b59a1…0c3c08
Audit this contract →
← previous block·next block →recent activity