← previous blocknext block →recent activity
Analyzing
Block #102,286,097
64 transactions · 59 stateful · 2026-09-05 21:02:02 UTC
Parallelism
94/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,286,097 · 64 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
1w010w058w159w260w361w162w063w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xef11437a…7718
0x065c9d…c394
6 touches
3 conflicts
0xd6a0b3e6…9014
0x065c9d…c394
5 touches
3 conflicts
0x9234519c…5397
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd3f00808…c74c
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x975a6dc0…055e
0x065c9d…c394
3 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