← previous blocknext block →recent activity
Analyzing
Block #86,325,238
13 transactions · 11 stateful · 2026-07-08 03:16:00 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,325,238 · 13 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
1w02w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x37709e82…8bf9
0x851145…3f07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3f20fc7f…8409
0x851145…3f07
3 touches
1 conflict
0x61c7745d…122b
0x851145…3f07
3 touches
1 conflict
0xc1f1387f…cb61
0x40c49f…2af0
2 touches
0 conflicts
0xe8a2dc06…02ec
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 0x22e0cc1d4a…90ad04
Audit this contract →
← previous block·next block →recent activity