Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d9bf96fc72cc9df3192cb358647520254db70d234ae617cbc0b3a72248daf79

Tx prefix hash: a025043741ad71dbd0ebf78c7323d1de1f208bd7bd471dd49ac842d68a3b42e1
Tx public key: d3c575531483d2566d9469b1be157be9f9f9a9bf3edb943126d4ef2d72227fde
Timestamp: 1759041414 Timestamp [UCT]: 2025-09-28 06:36:54 Age [y:d:h:m:s]: 00:010:00:23:14
Block: 1378105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7174 RingCT/type: yes/0
Extra: 01d3c575531483d2566d9469b1be157be9f9f9a9bf3edb943126d4ef2d72227fde021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36921755872d6c941fd13d452cb4210b5e0fc9baf424dabe67b39d4ea909ddb4 0.600000000000 1866200 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": 1378115, "vin": [ { "gen": { "height": 1378105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36921755872d6c941fd13d452cb4210b5e0fc9baf424dabe67b39d4ea909ddb4" } } ], "extra": [ 1, 211, 197, 117, 83, 20, 131, 210, 86, 109, 148, 105, 177, 190, 21, 123, 233, 249, 249, 169, 191, 62, 219, 148, 49, 38, 212, 239, 45, 114, 34, 127, 222, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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