← previous blocknext block →recent activity
Analyzing
Block #86,855,398
18 transactions · 17 stateful · 2026-07-10 14:21:08 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,855,398 · 18 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
2w03w14w25w06w17w28w29w312w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d64d7f8…ce93
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb0446875…2b96
0x34b655…2a6f
6 touches
3 conflicts
0xfcb950e3…7273
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
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 0x9d64d7f8fe…8bce93
Audit this contract →
← previous block·next block →recent activity