← previous blocknext block →recent activity
Analyzing
Block #100,855,433
34 transactions · 27 stateful · 2026-08-31 20:49:01 UTC
Parallelism
91/100
Blocked
30%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,855,433 · 34 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w110w111w213w015w123w024w126w232w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x7e28e55c…d05c
0x754704…b603
4 touches
1 conflict
0x00000000…0001
0x659bd0…a9da
4 touches
1 conflict
0x00000000…0000
0x659bd0…a9da
4 touches
1 conflict
0x98d84ddb…29c5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xeb88ed4e…a342
0x34b655…2a6f
4 touches
1 conflict
0x50951f37…219c
0x3bd359…433a
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
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity