← previous blocknext block →recent activity
Analyzing
Block #100,749,160
24 transactions · 22 stateful · 2026-08-31 11:54:00 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,749,160 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w310w011w112w213w014w115w216w317w419w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0xdd6a5b47…f3e7
0x851145…3f07
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c0
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
10 conflicts on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity