← previous blocknext block →recent activity
Analyzing
Block #100,894,452
24 transactions · 21 stateful · 2026-09-01 00:05:17 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,894,452 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w19w218w319w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa09be5a…1e79
0x34b655…2a6f
6 touches
3 conflicts
0x168b8892…f447
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x92d8dee2…256b
0x34b655…2a6f
4 touches
1 conflict
0xbf303bde…ce5a
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 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
3 conflicts on slot 0xfa09be5aaf…9b1e79
Audit this contract →
← previous block·next block →recent activity