← previous blocknext block →recent activity
Analyzing
Block #100,704,100
14 transactions · 13 stateful · 2026-08-31 08:07:20 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,704,100 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w19w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
6 touches
3 conflicts
0x71717491…10cf
0xa6afd3…d132
6 touches
3 conflicts
0xe1dc0f7d…7004
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
2 touches
0 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity