← previous blocknext block →recent activity
Analyzing
Block #102,213,613
21 transactions · 13 stateful · 2026-09-05 14:54:42 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,213,613 · 21 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
3w06w07w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x01f335d6…0270
0x065c9d…c394
4 touches
1 conflict
0xcea8441f…f9aa
0x065c9d…c394
3 touches
1 conflict
0x2da4b2c5…4d1f
0x065c9d…c394
3 touches
1 conflict
0x699c7b27…96e6
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
3 conflicts on slot 0x77ed432f03…d6fa04
Audit this contract →
← previous block·next block →recent activity