Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84cce21325a58bc01703fcfd191aaef50b9b03e7bd0de86a3537d63ba20947f4

Tx prefix hash: 8d21aa67c74f600ec7891958427b6c6a721406797ebdc2c9f82890cb7db7145a
Tx public key: 975c07d5fe5d6f1ac7e5c823bed280d3efbf72fcd6f021a5ccc20dbe8cf3d497
Timestamp: 1741196477 Timestamp [UCT]: 2025-03-05 17:41:17 Age [y:d:h:m:s]: 00:267:16:24:13
Block: 1232824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189072 RingCT/type: yes/0
Extra: 01975c07d5fe5d6f1ac7e5c823bed280d3efbf72fcd6f021a5ccc20dbe8cf3d4970211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e64d069107d73be0430fbf48445c8e176dec0babafefdc1e6a9aec28e8d6d5 0.600000000000 1719739 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": 1232834, "vin": [ { "gen": { "height": 1232824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e64d069107d73be0430fbf48445c8e176dec0babafefdc1e6a9aec28e8d6d5" } } ], "extra": [ 1, 151, 92, 7, 213, 254, 93, 111, 26, 199, 229, 200, 35, 190, 210, 128, 211, 239, 191, 114, 252, 214, 240, 33, 165, 204, 194, 13, 190, 140, 243, 212, 151, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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