← previous blocknext block →recent activity
Analyzing
Block #86,741,303
23 transactions · 22 stateful · 2026-07-10 01:38:41 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,741,303 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w111w012w114w215w316w118w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x93d4b4e9…5daa
0x851145…3f07
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8d0d8061…d410
0xc8689a…ee79
6 touches
3 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 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: 0x851145ea…9f3f07
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity