← previous blocknext block →recent activity
Analyzing
Block #99,700,927
14 transactions · 14 stateful · 2026-08-27 19:49:34 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,700,927 · 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
2w03w04w05w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13ddf3fe…d370
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdad20621…06b1
0x34b655…2a6f
4 touches
1 conflict
0x5d5bad6c…76cc
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x67e46082…d438
0x34b655…2a6f
2 touches
0 conflicts
0x69c844bd…c9de
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 0x13ddf3fe71…32d370
Audit this contract →
← previous block·next block →recent activity