Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ac817f1119756249ee4cd0580b8b18fcff6b9339d5b3c46f29d8bde21a1a3f

Tx prefix hash: 242ab90a0b22e89ca50b7f05b1eb9374d22982c8fbcb62c000fa6a9515a0f947
Tx public key: f23b97ba170190e3fe76e8d08f30470bb689d1057253f3c681295239d4a2f3b6
Timestamp: 1577671829 Timestamp [UCT]: 2019-12-30 02:10:29 Age [y:d:h:m:s]: 05:307:17:32:56
Block: 34704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367440 RingCT/type: yes/0
Extra: 01f23b97ba170190e3fe76e8d08f30470bb689d1057253f3c681295239d4a2f3b602110000000ad81c26c0000000000000000000

1 output(s) for total of 470.998575441000 dcy

stealth address amount amount idx
00: d8f14260cfdb2f2ccc9a513fd53193c73aefb3372a186578f212445e0b69a671 470.998575441000 58446 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": 34714, "vin": [ { "gen": { "height": 34704 } } ], "vout": [ { "amount": 470998575441, "target": { "key": "d8f14260cfdb2f2ccc9a513fd53193c73aefb3372a186578f212445e0b69a671" } } ], "extra": [ 1, 242, 59, 151, 186, 23, 1, 144, 227, 254, 118, 232, 208, 143, 48, 71, 11, 182, 137, 209, 5, 114, 83, 243, 198, 129, 41, 82, 57, 212, 162, 243, 182, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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