← previous blocknext block →recent activity
Analyzing
Block #100,631,578
24 transactions · 19 stateful · 2026-08-31 02:02:33 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,631,578 · 24 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
1w02w13w04w15w27w210w012w114w216w018w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xb8b13faa…9e11
0x065c9d…c394
4 touches
1 conflict
0xfa05c722…81a8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
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