← previous blocknext block →recent activity
Analyzing
Block #108,927,761
21 transactions · 19 stateful · 2026-09-29 03:20:10 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,927,761 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w19w211w012w114w115w116w118w019w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dce5f78…29c5
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x8950ca03…672e
0xd32edf…ff58
5 touches
3 conflicts
0x842db5f1…6d50
0x1b6862…e19c
4 touches
1 conflict
0x9940c96a…6e77
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 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: ShMonad (shMON)
3 conflicts on slot 0x9dce5f78d3…f529c5
Audit this contract →
← previous block·next block →recent activity