Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80b8c3335ef115e9f5614e455669fdc1fca133553837f3f89215eb0fc5bb0db8

Tx prefix hash: ffe4315eb528157583380e24c6ba21c4cffe9d14a520efb5bda1c44a20e5d3c0
Tx public key: 4da583c0666de842d2e2a6c111e239d6fd75dbeb8d93c957fc7348a5114cc690
Timestamp: 1732870869 Timestamp [UCT]: 2024-11-29 09:01:09 Age [y:d:h:m:s]: 00:131:18:24:36
Block: 1164161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93986 RingCT/type: yes/0
Extra: 014da583c0666de842d2e2a6c111e239d6fd75dbeb8d93c957fc7348a5114cc690021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4479364829f3d9a771aa6ca334ac817f63ab4da5689f0aabd8229d1b4c918327 0.600000000000 1649834 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": 1164171, "vin": [ { "gen": { "height": 1164161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4479364829f3d9a771aa6ca334ac817f63ab4da5689f0aabd8229d1b4c918327" } } ], "extra": [ 1, 77, 165, 131, 192, 102, 109, 232, 66, 210, 226, 166, 193, 17, 226, 57, 214, 253, 117, 219, 235, 141, 147, 201, 87, 252, 115, 72, 165, 17, 76, 198, 144, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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