← previous blocknext block →recent activity
Analyzing
Block #100,135,970
13 transactions · 12 stateful · 2026-08-29 08:24:58 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,135,970 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05d3b9a3…0a91
0x34b655…2a6f
2 touches
0 conflicts
0x373c62f9…49e8
0x34b655…2a6f
2 touches
0 conflicts
0x437812ac…80d9
0x34b655…2a6f
2 touches
0 conflicts
0x4fce3905…6f4f
0x34b655…2a6f
2 touches
0 conflicts
0x50c61506…343f
0x34b655…2a6f
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
1 conflict on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity