Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ccab201e4e7b4480516bf650222dac3f1a8352714dc6b304ea021d6d483ccd

Tx prefix hash: c02a1ca7f0ad61bb450bc8c444ef669ed2257c334ef9abcdf537aafe4ab7a5ec
Tx public key: 99246c8c8377b9c00f16c2df7b6084e5dc2f86834beed61f89f69bfe65bf0ec4
Timestamp: 1760685159 Timestamp [UCT]: 2025-10-17 07:12:39 Age [y:d:h:m:s]: 00:079:08:38:29
Block: 1391746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56831 RingCT/type: yes/0
Extra: 0199246c8c8377b9c00f16c2df7b6084e5dc2f86834beed61f89f69bfe65bf0ec40211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0918268deebb13f50447a97472538e1cca8b0bd753d192e5237fcc3ec5c5a775 0.600000000000 1879993 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 dinasty-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": 1391756, "vin": [ { "gen": { "height": 1391746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0918268deebb13f50447a97472538e1cca8b0bd753d192e5237fcc3ec5c5a775" } } ], "extra": [ 1, 153, 36, 108, 140, 131, 119, 185, 192, 15, 22, 194, 223, 123, 96, 132, 229, 220, 47, 134, 131, 75, 238, 214, 31, 137, 246, 155, 254, 101, 191, 14, 196, 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): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8