← previous blocknext block →recent activity
Analyzing
Block #106,028,603
27 transactions · 18 stateful · 2026-09-19 00:01:01 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,028,603 · 27 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
5w014w015w016w117w218w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2681e5c5…faac
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11683432…a708
0xd32edf…ff58
5 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
2 touches
0 conflicts
0x00000000…0001
0x2d82ac…5fd8
2 touches
0 conflicts
0x00000000…0005
0x2d82ac…5fd8
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
3 conflicts on slot 0x2681e5c5ca…c0faac
Audit this contract →
← previous block·next block →recent activity