← previous blocknext block →recent activity
Analyzing
Block #86,340,430
14 transactions · 12 stateful · 2026-07-08 04:57:27 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,340,430 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x3a84c2f2…892e
0x851145…3f07
4 touches
1 conflict
0x4655af35…9f9b
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x7f8804d2…902d
0x34b655…2a6f
3 touches
1 conflict
0xeba726d9…869d
0x40c49f…2af0
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
3 conflicts on slot 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity