Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a83b6edef7627f5fad9dab5e0a437afc0728ca99d2e2b3bd2fa7fe1958cdba

Tx prefix hash: 531cc47776f6e9d6fb0f8385c67cf4fd658a807e01dbb545b2ceb21799a16eb6
Tx public key: 83e867209fff74c0bcfd1648a9019bb1d008e9d68d966f77e10028e2c2590106
Timestamp: 1672513829 Timestamp [UCT]: 2022-12-31 19:10:29 Age [y:d:h:m:s]: 02:060:11:49:58
Block: 664732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564903 RingCT/type: yes/0
Extra: 0183e867209fff74c0bcfd1648a9019bb1d008e9d68d966f77e10028e2c259010602110000000233af99f4000000000000000000

1 output(s) for total of 3.850054751000 dcy

stealth address amount amount idx
00: a495d9456f779c5e3a908a7bd3eee691806714946909d6b2255c5559b48c0d67 3.850054751000 1105737 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": 664742, "vin": [ { "gen": { "height": 664732 } } ], "vout": [ { "amount": 3850054751, "target": { "key": "a495d9456f779c5e3a908a7bd3eee691806714946909d6b2255c5559b48c0d67" } } ], "extra": [ 1, 131, 232, 103, 32, 159, 255, 116, 192, 188, 253, 22, 72, 169, 1, 155, 177, 208, 8, 233, 214, 141, 150, 111, 119, 225, 0, 40, 226, 194, 89, 1, 6, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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