← previous blocknext block →recent activity
Analyzing
Block #101,093,964
32 transactions · 23 stateful · 2026-09-01 16:49:20 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,093,964 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w114w016w318w421w126w430w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x892daf6e…48d8
0x065c9d…c394
10 touches
10 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
8 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
8 touches
6 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xed863ec8…90d6
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity