← previous blocknext block →recent activity
Analyzing
Block #101,150,033
17 transactions · 13 stateful · 2026-09-01 21:31:23 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,150,033 · 17 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
1w03w15w27w08w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x34de0151…3309
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xb87af72ae5…0baef6
Audit this contract →
← previous block·next block →recent activity