← previous blocknext block →recent activity
Analyzing
Block #86,713,470
22 transactions · 16 stateful · 2026-07-09 22:32:38 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,713,470 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w010w011w112w213w214w318w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x6f845aff…9fc9
0x3bd359…433a
6 touches
3 conflicts
0x062b2598…4e28
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0000
0x4b6ce4…7f37
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0003
0x4b6ce4…7f37
6 touches
3 conflicts
0xe8b6e4c2…e20a
0x188d58…ea8e
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: Perpl
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity