← previous blocknext block →recent activity
Analyzing
Block #102,190,200
17 transactions · 16 stateful · 2026-09-05 12:56:02 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,190,200 · 17 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
1w02w03w05w06w18w09w112w213w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xe108b282…58b3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x3bc090c8…9c23
0xd32edf…ff58
3 touches
1 conflict
0xf1eba5c4…1b68
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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 0x77ed432f03…d6fa04
Audit this contract →
← previous block·next block →recent activity