← previous blocknext block →recent activity
Analyzing
Block #86,302,405
24 transactions · 20 stateful · 2026-07-08 00:43:23 UTC
Parallelism
79/100
Blocked
65%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,302,405 · 24 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
1w02w03w15w26w38w09w111w012w213w314w115w116w417w318w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d488000…3831
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x1a3ca58e…6490
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa19aba84…8922
0xa6afd3…d132
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
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
6 conflicts on slot 0x0d488000e2…143831
Audit this contract →
← previous block·next block →recent activity