← previous blocknext block →recent activity
Analyzing
Block #101,067,095
21 transactions · 19 stateful · 2026-09-01 14:33:57 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,067,095 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w314w315w416w118w520w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e677f5…e3bd
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x831f75b4…945d
0x34b655…2a6f
6 touches
3 conflicts
0xdf93c009…d51f
0x851145…3f07
4 touches
1 conflict
0xb2e9ab60…6e48
0x34b655…2a6f
4 touches
1 conflict
0xbdee5a85…e800
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
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 0x70e677f5c0…90e3bd
Audit this contract →
← previous block·next block →recent activity