← previous blocknext block →recent activity
Analyzing
Block #99,490,098
14 transactions · 14 stateful · 2026-08-27 01:59:54 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,490,098 · 14 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
5w06w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4de9708f…56d0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x10829102…94c2
0x34b655…2a6f
2 touches
0 conflicts
0x128fb0bd…18e5
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
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 0x0ed7cc0b4b…d2ee52
Audit this contract →
← previous block·next block →recent activity