← previous blocknext block →recent activity
Analyzing
Block #100,923,327
24 transactions · 23 stateful · 2026-09-01 02:30:31 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,923,327 · 24 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
1w02w13w24w05w110w012w213w314w415w516w617w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x9bdc5ef9…0695
0x065c9d…c394
6 touches
3 conflicts
0xd5f34512…488d
0x065c9d…c394
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x249bd738…17f5
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0a85a226…83bf
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
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity