← previous blocknext block →recent activity
Analyzing
Block #102,039,378
17 transactions · 16 stateful · 2026-09-05 00:11:23 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,039,378 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w49w510w612w013w114w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x928d6b23…5370
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
14 touches
21 conflicts
0x1e3984a8…cbe1
0xd32edf…ff58
13 touches
21 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…000012
Audit this contract →
← previous block·next block →recent activity