← previous blocknext block →recent activity
Analyzing
Block #102,428,807
80 transactions · 53 stateful · 2026-09-06 09:04:59 UTC
Parallelism
80/100
Blocked
72%
Avg conflicts / tx
2.44
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #102,428,807 · 80 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w07w09w110w211w312w413w116w017w018w119w220w321w422w523w624w725w830w233w470w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
32 touches
120 conflicts
0x5f77d607…2c84
0x065c9d…c394
30 touches
105 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
26 touches
78 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
26 touches
78 conflicts
0x06e40499…165e
0x34ae4d…3fc5
26 touches
78 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
16 touches
28 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-MON/USDC
120 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity