← previous blocknext block →recent activity
Analyzing
Block #100,750,246
17 transactions · 17 stateful · 2026-08-31 11:59:28 UTC
Parallelism
53/100
Blocked
65%
Avg conflicts / tx
2.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,750,246 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w28w310w311w312w413w514w615w716w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x0ebd0359…77d9
0x851145…3f07
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x792299c4…16b2
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity