← previous blocknext block →recent activity
Analyzing
Block #86,836,797
29 transactions · 21 stateful · 2026-07-10 12:16:49 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,836,797 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w112w014w115w219w020w121w022w123w124w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xfed09e59…a493
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x45d87399…4382
0x34b655…2a6f
4 touches
1 conflict
0x5464594e…d6e0
0x34b655…2a6f
4 touches
1 conflict
0x5a310d83…cae0
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity