← previous blocknext block →recent activity
Analyzing
Block #99,084,232
17 transactions · 16 stateful · 2026-08-25 15:56:56 UTC
Parallelism
76/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,084,232 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w112w215w016w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e1c65d0…77a3
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x17590de4…d38a
0x34b655…2a6f
4 touches
1 conflict
0x4a53d006…2944
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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
3 conflicts on slot 0x9e1c65d07e…4077a3
Audit this contract →
← previous block·next block →recent activity