Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63247a4b3d7ced6f29a087eab4fdc65fc6491bfe8c3bcaad1c54e0bb62748e70

Tx prefix hash: bf11ce66b7491ffbd897d2960bfb562d753abbb57d39cc911be947099ecd611e
Tx public key: e505ff2ed1a99e4b4d7b6c1d5e038f56f4a4e71197ef1fe07f2ddd5ad41d266b
Timestamp: 1792505454 Timestamp [UTC]: 2026-10-20 14:10:54 Age [y:d:h:m:s]: 00:033:04:11:41
Block: 1658654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 24840 RingCT/type: yes/0
Extra: 01e505ff2ed1a99e4b4d7b6c1d5e038f56f4a4e71197ef1fe07f2ddd5ad41d266b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e6fc4ddeaf3142753209a193e870e81aa53eb9bf909301c76ba3c8c7f6990a3 0.000600000000 2149412 of 15 <68>

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": 1658664, "vin": [ { "gen": { "height": 1658654 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4e6fc4ddeaf3142753209a193e870e81aa53eb9bf909301c76ba3c8c7f6990a3", "view_tag": "68" } } } ], "extra": [ 1, 229, 5, 255, 46, 209, 169, 158, 75, 77, 123, 108, 29, 94, 3, 143, 86, 244, 164, 231, 17, 151, 239, 31, 224, 127, 45, 221, 90, 212, 29, 38, 107 ], "rct_signatures": { "type": 0 } }


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