← previous blocknext block →recent activity
Analyzing
Block #100,585,184
20 transactions · 16 stateful · 2026-08-30 22:09:09 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,585,184 · 20 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
2w03w14w26w08w19w312w015w116w217w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf17a42a3…4069
0x065c9d…c394
6 touches
3 conflicts
0x8b025501…d8e7
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0xebc92c…1be1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity