← previous blocknext block →recent activity
Analyzing
Block #86,299,326
21 transactions · 18 stateful · 2026-07-08 00:22:50 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,299,326 · 21 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
1w02w15w010w013w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x46b62326…9b3c
0xa6afd3…d132
4 touches
1 conflict
0x89750670…2dea
0xa6afd3…d132
4 touches
1 conflict
0x968d497f…24d0
0xd32edf…ff58
3 touches
1 conflict
0xba76f1ea…f06c
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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 0x966e45cf3c…9f0f25
Audit this contract →
← previous block·next block →recent activity