Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd05625e780b6b1a4e618bb7b7632885ab95c861828d7962c6107c6d4d5bc7f5

Tx prefix hash: 6cef0a7ca52d567db7e365bf8dc54e1b9a92c75f20f76cb9ca385aa52dd585ae
Tx public key: 7ef18d65868a58d0b3f81e99e316857704c255cf873ee055d33302bbe3837d90
Timestamp: 1775264902 Timestamp [UTC]: 2026-04-04 01:08:22 Age [y:d:h:m:s]: 00:224:01:34:36
Block: 1512317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165508 RingCT/type: yes/0
Extra: 017ef18d65868a58d0b3f81e99e316857704c255cf873ee055d33302bbe3837d90021100000007ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd9ca7ce0e1fa1ec7cd4f3bb76e738848785a48bdd8d81636dbfa2f46c00ee60 0.000600000000 2002117 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": 1512327, "vin": [ { "gen": { "height": 1512317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd9ca7ce0e1fa1ec7cd4f3bb76e738848785a48bdd8d81636dbfa2f46c00ee60" } } ], "extra": [ 1, 126, 241, 141, 101, 134, 138, 88, 208, 179, 248, 30, 153, 227, 22, 133, 119, 4, 194, 85, 207, 135, 62, 224, 85, 211, 51, 2, 187, 227, 131, 125, 144, 2, 17, 0, 0, 0, 7, 238, 75, 113, 129, 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: