← previous blocknext block →recent activity
Analyzing
Block #102,740,902
32 transactions · 29 stateful · 2026-09-07 11:22:36 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,740,902 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w310w011w112w213w314w415w516w125w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
12 touches
15 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
12 touches
15 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x519fd77d…46b4
0x065c9d…c394
6 touches
9 conflicts
0x99deb5b6…d526
0x065c9d…c394
6 touches
9 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity