← previous blocknext block →recent activity
Analyzing
Block #102,446,138
38 transactions · 32 stateful · 2026-09-06 10:32:36 UTC
Parallelism
82/100
Blocked
34%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,446,138 · 38 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w29w015w119w321w027w228w029w130w433w534w535w636w037w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x17a86c95…e58a
0x065c9d…c394
5 touches
3 conflicts
0x74e485b1…d380
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