← previous blocknext block →recent activity
Analyzing
Block #102,481,666
17 transactions · 17 stateful · 2026-09-06 13:32:45 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,481,666 · 17 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
2w03w14w15w06w17w010w111w212w213w314w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xebe581d8…2696
0x34b655…2a6f
6 touches
3 conflicts
0x22f10271…841d
0x34b655…2a6f
6 touches
3 conflicts
0xa918f7f0…f410
0x34b655…2a6f
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbc0de6fd…ea8d
0x34b655…2a6f
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: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity