← previous blocknext block →recent activity
Analyzing
Block #100,607,703
32 transactions · 25 stateful · 2026-08-31 00:02:26 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,607,703 · 32 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
1w02w04w05w110w012w113w215w118w222w328w029w131w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x776d8eb0…21ee
0x065c9d…c394
6 touches
3 conflicts
0xc813c9e3…390a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x78694995…f66e
0x1b6862…e19c
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
6 conflicts on slot 0x1125877469…519892
Audit this contract →
← previous block·next block →recent activity