Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ddff1db4f9e0f24ae3fbfe1182e49659772312d654d893fe4f52966974e8a255

Tx prefix hash: 8007b6e2f8cc5ee9bc4d59a3a2adb008c8e457a535bbd7bb4ef60a5d76d2e703
Tx public key: dbaf2890fb895f3811ba37e8cd6191de44c5e03958aad9aa98e96858201448ad
Timestamp: 1761048095 Timestamp [UTC]: 2025-10-21 12:01:35 Age [y:d:h:m:s]: 01:031:08:49:05
Block: 1394752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288742 RingCT/type: yes/0
Extra: 01dbaf2890fb895f3811ba37e8cd6191de44c5e03958aad9aa98e96858201448ad0211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e9e05de2d93831da0df2467b7bae3a1dc3c41f5c3e4ffcc4e91f7eeee4305c4 0.000600000000 1883027 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1394762, "vin": [ { "gen": { "height": 1394752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9e05de2d93831da0df2467b7bae3a1dc3c41f5c3e4ffcc4e91f7eeee4305c4" } } ], "extra": [ 1, 219, 175, 40, 144, 251, 137, 95, 56, 17, 186, 55, 232, 205, 97, 145, 222, 68, 197, 224, 57, 88, 170, 217, 170, 152, 233, 104, 88, 32, 20, 72, 173, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: