← previous blocknext block →recent activity
Analyzing
Block #102,737,141
11 transactions · 11 stateful · 2026-09-07 11:03:41 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,737,141 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x11ed6366…87c4
0x065c9d…c394
3 touches
1 conflict
0x196d0c7b…27c1
0x065c9d…c394
3 touches
1 conflict
0x8b9e2d47…9675
0x188d58…ea8e
2 touches
0 conflicts
0x1342557a…df31
0x27bc99…9a93
2 touches
0 conflicts
0xb3dee783…2711
0x27bc99…9a93
2 touches
0 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity