← previous blocknext block →recent activity
Analyzing
Block #108,918,497
27 transactions · 22 stateful · 2026-09-29 02:33:27 UTC
Parallelism
59/100
Blocked
73%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #108,918,497 · 27 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w58w69w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x792299c4…16b6
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0xde6a2c2d…35bc
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0056
0x1b6862…e19c
16 touches
28 conflicts
0x5eb5c837…6f7d
0x1b6862…e19c
16 touches
28 conflicts
0x932f03f1…8b49
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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: ShMonad (shMON)
36 conflicts on slot 0x792299c4aa…cc16b6
Audit this contract →
← previous block·next block →recent activity