← previous blocknext block →recent activity
Analyzing
Block #86,664,713
10 transactions · 9 stateful · 2026-07-09 17:07:16 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,664,713 · 10 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6805ef8…e22e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x0916de51…868a
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0xa6afd3…d132
2 touches
0 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
2 touches
0 conflicts
0x002a0f9e…b33b
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0xa8abcc19…3d83
0xea1b8e…c5ec
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 0xe6805ef89e…4fe22e
Audit this contract →
← previous block·next block →recent activity