← previous blocknext block →recent activity
Analyzing
Block #108,103,321
23 transactions · 20 stateful · 2026-09-26 06:06:52 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,103,321 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w18w210w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xba5743c7…21c3
0x1b6862…e19c
14 touches
21 conflicts
0xfe39b603…7c75
0xd32edf…ff58
13 touches
21 conflicts
0x74e485b1…d380
0x34b655…2a6f
12 touches
15 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
10 touches
10 conflicts
0x451e482b…7e7d
0x34b655…2a6f
10 touches
10 conflicts
0x45885570…ed97
0x34b655…2a6f
10 touches
10 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)
21 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity