← previous blocknext block →recent activity
Analyzing
Block #101,092,141
20 transactions · 20 stateful · 2026-09-01 16:40:10 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,092,141 · 20 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
1w02w03w14w25w06w18w29w312w213w017w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0x8ff177db…05ca
0x065c9d…c394
4 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity