← previous blocknext block →recent activity
Analyzing
Block #100,627,346
15 transactions · 14 stateful · 2026-08-31 01:41:15 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,627,346 · 15 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
1w02w13w28w09w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x68106229…7057
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
4 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
4 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
4 touches
1 conflict
0xdb067026…9eb8
0x34ae4d…3fc5
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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity