Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67cef9f5da40ac4b53768581fd00e8dbce5677836dfee6948068b722d38960a2

Tx prefix hash: e6813ee27f9524245d4b7dae47cb8c2a1a3159a6a5474146d641649e58452e6c
Tx public key: 8c1b5ad458b64ecd9446efe71bfd74d0eb9e202ded00c17989cbec9ba575407f
Timestamp: 1577484388 Timestamp [UCT]: 2019-12-27 22:06:28 Age [y:d:h:m:s]: 04:339:01:14:22
Block: 33103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131486 RingCT/type: yes/0
Extra: 018c1b5ad458b64ecd9446efe71bfd74d0eb9e202ded00c17989cbec9ba575407f02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 476.795205009000 dcy

stealth address amount amount idx
00: 84e298686a190a1c6a6288cbb030b4537fb2585996ddd1e57df88b4e592023f2 476.795205009000 55281 of 0

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": 33113, "vin": [ { "gen": { "height": 33103 } } ], "vout": [ { "amount": 476795205009, "target": { "key": "84e298686a190a1c6a6288cbb030b4537fb2585996ddd1e57df88b4e592023f2" } } ], "extra": [ 1, 140, 27, 90, 212, 88, 182, 78, 205, 148, 70, 239, 231, 27, 253, 116, 208, 235, 158, 32, 45, 237, 0, 193, 121, 137, 203, 236, 155, 165, 117, 64, 127, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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