← previous blocknext block →recent activity
Analyzing
Block #86,227,438
17 transactions · 15 stateful · 2026-07-07 16:22:51 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,227,438 · 17 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
1w02w04w08w19w110w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0xfda40dbf…ff3a
0x40c49f…2af0
3 touches
1 conflict
0x5d431ee2…4319
0x40c49f…2af0
3 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
1 conflict on slot 0xb9b077a82b…59e029
Audit this contract →
← previous block·next block →recent activity