← previous blocknext block →recent activity
Analyzing
Block #86,104,899
12 transactions · 12 stateful · 2026-07-07 02:44:44 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,104,899 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ed530e…fa7d
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x059ed451…80de
0x40c49f…2af0
2 touches
0 conflicts
0xab222fe8…da10
0x40c49f…2af0
2 touches
0 conflicts
0xb612589e…cba8
0x40c49f…2af0
2 touches
0 conflicts
0xcd5749c2…e580
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
1 conflict on slot 0xc6ed530ecc…a9fa7d
Audit this contract →
← previous block·next block →recent activity