← previous blocknext block →recent activity
Analyzing
Block #100,856,820
22 transactions · 20 stateful · 2026-08-31 20:56:00 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,856,820 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w113w214w315w416w517w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0xacaca711…268f
0x40c49f…2af0
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7691bb4f…bb88
0x065c9d…c394
4 touches
1 conflict
0x856cdad4…3e7b
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
15 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity