← previous blocknext block →recent activity
Analyzing
Block #100,636,030
53 transactions · 38 stateful · 2026-08-31 02:24:56 UTC
Parallelism
81/100
Blocked
71%
Avg conflicts / tx
1.66
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,636,030 · 53 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w49w510w618w719w840w141w245w251w352w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
18 touches
36 conflicts
0x88ecacda…04c9
0xa6afd3…d132
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
14 touches
21 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
14 touches
21 conflicts
0xa987699f…eabe
0x34ae4d…3fc5
14 touches
21 conflicts
0x10abefc9…c9bc
0x34ae4d…3fc5
14 touches
21 conflicts
0x10d80fee…dbda
0x34ae4d…3fc5
14 touches
21 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
36 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity