← previous blocknext block →recent activity
Analyzing
Block #86,712,623
16 transactions · 13 stateful · 2026-07-09 22:26:58 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,712,623 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w210w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00cd9338…40d2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x813d6148…7e8f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcbe18c62…3a5d
0x34b655…2a6f
4 touches
1 conflict
0x72d7e5ed…a96b
0x34b655…2a6f
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
3 conflicts on slot 0x00cd933805…2240d2
Audit this contract →
← previous block·next block →recent activity