← previous blocknext block →recent activity
Analyzing
Block #108,683,451
28 transactions · 24 stateful · 2026-09-28 06:47:09 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,683,451 · 28 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
1w02w04w16w27w39w112w013w214w315w416w317w419w420w523w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3483764…f296
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x87322317…b559
0xd32edf…ff58
9 touches
10 conflicts
0x9e9a67c9…e68c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00369439…2286
0x34b655…2a6f
8 touches
6 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)
10 conflicts on slot 0xc34837646d…35f296
Audit this contract →
← previous block·next block →recent activity