← previous blocknext block →recent activity
Analyzing
Block #100,923,944
9 transactions · 9 stateful · 2026-09-01 02:33:38 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,923,944 · 9 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
1w02w13w24w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x978bc645…da9f
0x065c9d…c394
5 touches
3 conflicts
0x353b03c9…8d93
0x065c9d…c394
2 touches
0 conflicts
0xfe13ffa1…b2af
0x065c9d…c394
2 touches
0 conflicts
0xff2e6eba…c051
0x065c9d…c394
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 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 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity