Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e6c029ff3d9b67d9c024111a219bd8eb95babfe8c8f9004cfca3df84aa5f505

Tx prefix hash: 6485a2edd468bc20b42c980d2fb6a7d2e73c30acf18c0628eff2f1d81baa6f85
Tx public key: 0c5095686446f586eda4730827d5a02bf20c09ec4a9ad079b89c0539034142f1
Timestamp: 1760740849 Timestamp [UCT]: 2025-10-17 22:40:49 Age [y:d:h:m:s]: 00:102:01:29:32
Block: 1392210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72883 RingCT/type: yes/0
Extra: 010c5095686446f586eda4730827d5a02bf20c09ec4a9ad079b89c0539034142f10211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a4ea055de58f401d89adb5579f8ced49aa7b1c61c198ceb23d1b6a58d8079f5 0.600000000000 1880461 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": 1392220, "vin": [ { "gen": { "height": 1392210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a4ea055de58f401d89adb5579f8ced49aa7b1c61c198ceb23d1b6a58d8079f5" } } ], "extra": [ 1, 12, 80, 149, 104, 100, 70, 245, 134, 237, 164, 115, 8, 39, 213, 160, 43, 242, 12, 9, 236, 74, 154, 208, 121, 184, 156, 5, 57, 3, 65, 66, 241, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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