← previous blocknext block →recent activity
Analyzing
Block #100,813,658
22 transactions · 20 stateful · 2026-08-31 17:18:41 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,813,658 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w09w010w111w212w113w314w116w117w219w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xce74d807…8716
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x354d92…66fb
6 touches
3 conflicts
0x00000000…0001
0x354d92…66fb
6 touches
3 conflicts
0xac33ff75…077b
0x354d92…66fb
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 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
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity