Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9dad6a9ed99d6ab91e9885d751fe6266258127c2eb8ccba468a79bae396f498

Tx prefix hash: 466fee2123d8af847cd0c297988fbce3658ba28c3f9dd0b25686d2ca7d7082dd
Tx public key: 092991516410643e89268970b6fbc53268219461a6b50f8bd593e069675eb8e1
Timestamp: 1771970095 Timestamp [UTC]: 2026-02-24 21:54:55 Age [y:d:h:m:s]: 00:268:13:38:34
Block: 1485069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197587 RingCT/type: yes/0
Extra: 01092991516410643e89268970b6fbc53268219461a6b50f8bd593e069675eb8e1021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa798c493dcc8d82d53f3139ac7dd3b47fc6b20dbd03e15a0ce993bcd5f13b00 0.000600000000 1974501 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": 1485079, "vin": [ { "gen": { "height": 1485069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa798c493dcc8d82d53f3139ac7dd3b47fc6b20dbd03e15a0ce993bcd5f13b00" } } ], "extra": [ 1, 9, 41, 145, 81, 100, 16, 100, 62, 137, 38, 137, 112, 182, 251, 197, 50, 104, 33, 148, 97, 166, 181, 15, 139, 213, 147, 224, 105, 103, 94, 184, 225, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: