Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa7c620cdb7fe61b13626c7667212068d510ff8bd016cfa17f25590d06becefc

Tx prefix hash: 48e049fffe0c4e829f972a19e54153c75f0fedc35cfc131b8aff02e4c902e35c
Tx public key: fc5622d4859aca2abba3e6c8c28d841c2335a2ddb9379667adfb7c0d0309732e
Timestamp: 1732822999 Timestamp [UCT]: 2024-11-28 19:43:19 Age [y:d:h:m:s]: 00:186:02:33:06
Block: 1163767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132860 RingCT/type: yes/0
Extra: 01fc5622d4859aca2abba3e6c8c28d841c2335a2ddb9379667adfb7c0d0309732e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a344792a872b687637e0e4b68e21c8d5f3caf2c34271a759ff67ba8e70c8e225 0.600000000000 1649436 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": 1163777, "vin": [ { "gen": { "height": 1163767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a344792a872b687637e0e4b68e21c8d5f3caf2c34271a759ff67ba8e70c8e225" } } ], "extra": [ 1, 252, 86, 34, 212, 133, 154, 202, 42, 187, 163, 230, 200, 194, 141, 132, 28, 35, 53, 162, 221, 185, 55, 150, 103, 173, 251, 124, 13, 3, 9, 115, 46, 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