← previous blocknext block →recent activity
Analyzing
Block #102,429,439
30 transactions · 24 stateful · 2026-09-06 09:08:11 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,429,439 · 30 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
2w03w18w110w013w116w222w023w224w328w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1ad1b24f…c6ce
0x34b655…2a6f
4 touches
1 conflict
0x1ca77b04…e7b6
0x34b655…2a6f
4 touches
1 conflict
0x2203fd37…e232
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity