← previous blocknext block →recent activity
Analyzing
Block #108,671,453
28 transactions · 24 stateful · 2026-09-28 05:46:43 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.93
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,671,453 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w410w511w612w713w818w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0018
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
18 touches
36 conflicts
0x6235638c…6436
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0028
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x0b313a8a…f690
0xd32edf…ff58
17 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 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 0x0000000000…000018
Audit this contract →
← previous block·next block →recent activity