Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1898250a537a7517e8ec166e20b047cc8aa4a92eb12c6d0ff3db4c12451c80b9

Tx prefix hash: 5e05a8f3a633ade73e39e2320acbffb521b9b6f518c62edb92bfd91601a58274
Tx public key: 8b2c15ad7cc485ff95a1a71cdf2e27c281c24f57bfba4ad48fb7889a7d2c9d88
Timestamp: 1577606345 Timestamp [UCT]: 2019-12-29 07:59:05 Age [y:d:h:m:s]: 05:002:12:13:57
Block: 34165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151777 RingCT/type: yes/0
Extra: 018b2c15ad7cc485ff95a1a71cdf2e27c281c24f57bfba4ad48fb7889a7d2c9d880211000000014943cd9f000000000000000000

1 output(s) for total of 472.931268147000 dcy

stealth address amount amount idx
00: e6b67defa6d56aae5b4c425440f7ad5fd4c920e8838619445818efc3314dd889 472.931268147000 57505 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": 34175, "vin": [ { "gen": { "height": 34165 } } ], "vout": [ { "amount": 472931268147, "target": { "key": "e6b67defa6d56aae5b4c425440f7ad5fd4c920e8838619445818efc3314dd889" } } ], "extra": [ 1, 139, 44, 21, 173, 124, 196, 133, 255, 149, 161, 167, 28, 223, 46, 39, 194, 129, 194, 79, 87, 191, 186, 74, 212, 143, 183, 136, 154, 125, 44, 157, 136, 2, 17, 0, 0, 0, 1, 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