← previous blocknext block →recent activity
Analyzing
Block #102,315,659
21 transactions · 19 stateful · 2026-09-05 23:31:43 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,315,659 · 21 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
1w02w14w05w06w18w212w117w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x354e383e…817c
0xa6afd3…d132
4 touches
1 conflict
0x9d929e0c…9421
0xa6afd3…d132
4 touches
1 conflict
0x0b104f98…d9ee
0xc8689a…ee79
4 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
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