← previous blocknext block →recent activity
Analyzing
Block #100,620,605
13 transactions · 11 stateful · 2026-08-31 01:07:21 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,620,605 · 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
3w04w05w06w17w18w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88ecacda…04c9
0xa6afd3…d132
4 touches
1 conflict
0x35271755…3d03
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xfa75029c…d62c
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0x641aed07…bcb9
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: Market-WETH/USDC
1 conflict on slot 0x88ecacda36…0e04c9
Audit this contract →
← previous block·next block →recent activity