← previous blocknext block →recent activity
Analyzing
Block #84,357,810
39 transactions · 23 stateful · 2026-06-29 00:37:42 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,357,810 · 39 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
1w02w13w26w18w09w110w222w023w124w025w326w028w332w133w235w336w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9b334941…fddc
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x67206125…ec2b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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…000015
Audit this contract →
← previous block·next block →recent activity