← previous blocknext block →recent activity
Analyzing
Block #102,877,371
6 transactions · 6 stateful · 2026-09-07 22:52:27 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,877,371 · 6 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x354e383e…817c
0xa6afd3…d132
4 touches
1 conflict
0x9d929e0c…9421
0xa6afd3…d132
4 touches
1 conflict
0xbe178671…fce2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x34ae4d…3fc5
2 touches
0 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
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 0x354e383ef8…eb817c
Audit this contract →
← previous block·next block →recent activity