← previous blocknext block →recent activity
Analyzing
Block #101,324,353
15 transactions · 14 stateful · 2026-09-02 12:08:24 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,324,353 · 15 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
1w02w13w07w18w211w012w313w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0x10d80fee…dbda
0x34ae4d…3fc5
4 touches
1 conflict
0x5cc231f5…f1cd
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6a9f
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6aa0
0x34ae4d…3fc5
4 touches
1 conflict
0xea8e47b0…abfe
0x34ae4d…3fc5
4 touches
1 conflict
0x36126dcb…ca1e
0x34b655…2a6f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity