← previous blocknext block →recent activity
Analyzing
Block #86,487,561
16 transactions · 14 stateful · 2026-07-08 21:20:45 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,487,561 · 16 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
1w03w04w16w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x647a9286…61c1
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xb7d86595…6540
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
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 0x62d6e82b38…66a750
Audit this contract →
← previous block·next block →recent activity