← previous blocknext block →recent activity
Analyzing
Block #100,879,709
28 transactions · 23 stateful · 2026-08-31 22:51:07 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,879,709 · 28 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
1w03w16w07w18w010w113w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7215c582…4224
0x065c9d…c394
3 touches
1 conflict
0x8f0873b8…461c
0x065c9d…c394
3 touches
1 conflict
0x66de0ce3…337a
0x188d58…ea8e
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