← previous blocknext block →recent activity
Analyzing
Block #86,361,336
18 transactions · 14 stateful · 2026-07-08 07:16:59 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,361,336 · 18 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
2w04w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x042c6ea2…7a9a
0x34b655…2a6f
3 touches
1 conflict
0x1ebe108b…72a0
0x34b655…2a6f
2 touches
0 conflicts
0x38ad75de…7c1e
0x34b655…2a6f
2 touches
0 conflicts
0xddd20e39…d524
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1542
0x34b655…2a6f
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity