← previous blocknext block →recent activity
Analyzing
Block #108,619,191
37 transactions · 32 stateful · 2026-09-28 01:23:30 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,619,191 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w09w110w012w013w115w216w017w118w019w120w225w226w327w430w135w336w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xf499b415…8c46
0xd32edf…ff58
7 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 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)
6 conflicts on slot 0xcb45d9d62a…b1cb87
Audit this contract →
← previous block·next block →recent activity