Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc02367edcb924ed21d7eb5f87c7f0b073a1a3caea3e4d5d6c69dc35f0b6149

Tx prefix hash: e8d79e46ecc14b5d12ad3a9112b74163c9fdc2c6d8582b38874d40e3efd41572
Tx public key: 7dfa3f05f57dd9982966bf11aeca47aae1f65327f1541f8e2ab184761b260314
Timestamp: 1753475719 Timestamp [UTC]: 2025-07-25 20:35:19 Age [y:d:h:m:s]: 01:119:13:24:39
Block: 1333317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350177 RingCT/type: yes/0
Extra: 017dfa3f05f57dd9982966bf11aeca47aae1f65327f1541f8e2ab184761b260314021100000007ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc70d33d05cf6f4e4928299ca9d5c1d3f19e9c7c79fceb02dd4ad7845d6daa0c 0.000600000000 1821116 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": 1333327, "vin": [ { "gen": { "height": 1333317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc70d33d05cf6f4e4928299ca9d5c1d3f19e9c7c79fceb02dd4ad7845d6daa0c" } } ], "extra": [ 1, 125, 250, 63, 5, 245, 125, 217, 152, 41, 102, 191, 17, 174, 202, 71, 170, 225, 246, 83, 39, 241, 84, 31, 142, 42, 177, 132, 118, 27, 38, 3, 20, 2, 17, 0, 0, 0, 7, 239, 34, 20, 133, 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: