Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c6776541617636b95220aea6ff2b5ccfc617335302de832233944075e3acef4

Tx prefix hash: 2d6070024f3fcf8f2671b53d4d94f25861a3e2a0aa70d1affb7758961710896b
Tx public key: df07700d04e9d64a7e5182335f5a806432bd48ade88820d3bd354a6a12f0d65e
Timestamp: 1579205524 Timestamp [UCT]: 2020-01-16 20:12:04 Age [y:d:h:m:s]: 05:058:19:15:11
Block: 47071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192137 RingCT/type: yes/0
Extra: 01df07700d04e9d64a7e5182335f5a806432bd48ade88820d3bd354a6a12f0d65e0211000000024943cd9f000000000000000000

1 output(s) for total of 428.590531916000 dcy

stealth address amount amount idx
00: 960068b53e5fb52b1108b0b61c0a3abee36428df0b7c7d9f2dd5b1f881563325 428.590531916000 86933 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": 47081, "vin": [ { "gen": { "height": 47071 } } ], "vout": [ { "amount": 428590531916, "target": { "key": "960068b53e5fb52b1108b0b61c0a3abee36428df0b7c7d9f2dd5b1f881563325" } } ], "extra": [ 1, 223, 7, 112, 13, 4, 233, 214, 74, 126, 81, 130, 51, 95, 90, 128, 100, 50, 189, 72, 173, 232, 136, 32, 211, 189, 53, 74, 106, 18, 240, 214, 94, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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