Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1ddff20d03e76e7ff15f0faba3662f4b12c5a961416f3995c127030126c33b

Tx prefix hash: ebc671137c74cddaa3f4deb4af4f386b513f4dc3c312c290d9133e625f93f966
Tx public key: e20cb303492d11345d964b2dbd6dbbefecbc7c90d137679c05d41cb5cdfdf03a
Timestamp: 1711222946 Timestamp [UCT]: 2024-03-23 19:42:26 Age [y:d:h:m:s]: 01:052:21:39:19
Block: 984807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298789 RingCT/type: yes/0
Extra: 01e20cb303492d11345d964b2dbd6dbbefecbc7c90d137679c05d41cb5cdfdf03a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c50a1731bc91c3ba5563cb908c303a581789ab693355c262384e1ec30063e857 0.600000000000 1444980 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": 984817, "vin": [ { "gen": { "height": 984807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c50a1731bc91c3ba5563cb908c303a581789ab693355c262384e1ec30063e857" } } ], "extra": [ 1, 226, 12, 179, 3, 73, 45, 17, 52, 93, 150, 75, 45, 189, 109, 187, 239, 236, 188, 124, 144, 209, 55, 103, 156, 5, 212, 28, 181, 205, 253, 240, 58, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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