← previous blocknext block →recent activity
Analyzing
Block #109,237,260
33 transactions · 26 stateful · 2026-09-30 05:21:33 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,237,260 · 33 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
1w03w06w17w110w211w314w015w118w021w122w225w426w028w129w331w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
8 touches
6 conflicts
0x6235638c…6439
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x1b607409…5854
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
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 0x0000000000…00001b
Audit this contract →
← previous block·next block →recent activity