Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28560b5d2ada132a83c63cb53b5e76f00c907922202103ddca5c0f6b7ab3251

Tx prefix hash: d71beb3e2038c2ab895958d27503452ecba623cc5533bee15f7e43133681a299
Tx public key: d446e3b449cf54a8212432e5e31053c8c223bd9958d4f4f8385123fb141e83f9
Timestamp: 1574190096 Timestamp [UCT]: 2019-11-19 19:01:36 Age [y:d:h:m:s]: 05:106:19:06:54
Block: 12729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1219276 RingCT/type: yes/0
Extra: 01d446e3b449cf54a8212432e5e31053c8c223bd9958d4f4f8385123fb141e83f902110000000166a80d00000000000000000000

1 output(s) for total of 556.960539248000 dcy

stealth address amount amount idx
00: 2a8d81b41884c92e12b8fe0d56348d5cb59025e6aedfd095e81642cb85a42d24 556.960539248000 14387 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": 12739, "vin": [ { "gen": { "height": 12729 } } ], "vout": [ { "amount": 556960539248, "target": { "key": "2a8d81b41884c92e12b8fe0d56348d5cb59025e6aedfd095e81642cb85a42d24" } } ], "extra": [ 1, 212, 70, 227, 180, 73, 207, 84, 168, 33, 36, 50, 229, 227, 16, 83, 200, 194, 35, 189, 153, 88, 212, 244, 248, 56, 81, 35, 251, 20, 30, 131, 249, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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