Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378bfd16b6d91e4932fedb9b5fdc1ee53c8e13330705974b89bde469a484034f

Tx prefix hash: 6c96a715d3db9c7d2c1ec92d81891fdf819cea4e56a95986f9b9824127d44680
Tx public key: e64cfbbbb1ab7cdbc78ca575d93b7395ffe7f8e63aa55b28139a6c55c7b8f560
Timestamp: 1733649304 Timestamp [UCT]: 2024-12-08 09:15:04 Age [y:d:h:m:s]: 00:138:22:59:20
Block: 1170621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99113 RingCT/type: yes/0
Extra: 01e64cfbbbb1ab7cdbc78ca575d93b7395ffe7f8e63aa55b28139a6c55c7b8f560021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38b71e1579772ca71979c0508a4f48f2f2cc0e1aff11a28200e99143808214f 0.600000000000 1656352 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": 1170631, "vin": [ { "gen": { "height": 1170621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38b71e1579772ca71979c0508a4f48f2f2cc0e1aff11a28200e99143808214f" } } ], "extra": [ 1, 230, 76, 251, 187, 177, 171, 124, 219, 199, 140, 165, 117, 217, 59, 115, 149, 255, 231, 248, 230, 58, 165, 91, 40, 19, 154, 108, 85, 199, 184, 245, 96, 2, 17, 0, 0, 0, 9, 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