← previous blocknext block →recent activity
Analyzing
Block #100,924,315
16 transactions · 15 stateful · 2026-09-01 02:35:30 UTC
Parallelism
56/100
Blocked
40%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,924,315 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
4 touches
1 conflict
0x358580a5…614e
0x065c9d…c394
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xfbecdbaf…f803
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x4213f1c0…219a
0x2a68ba…90c5
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
21 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity