Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef04d61cc17196783cf6a33fe52937f9553e77ab7fd3bcf01837f4ee0b206e10

Tx prefix hash: 1720729e9256458b4ad775cb1f1f4e4fbe9c5138751c5e92d3c49b0668585c62
Tx public key: af4fa8d2e6ccb48201e1ab7f6cfb46766edb99d5c5f239eefe716cf6f3be415c
Timestamp: 1671908745 Timestamp [UCT]: 2022-12-24 19:05:45 Age [y:d:h:m:s]: 02:317:10:33:04
Block: 659734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746266 RingCT/type: yes/0
Extra: 01af4fa8d2e6ccb48201e1ab7f6cfb46766edb99d5c5f239eefe716cf6f3be415c021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.999699481000 dcy

stealth address amount amount idx
00: fdaaed22bc3442ff015755becfd71ddb5a7f4e2f296f5ffa4aae3ae6347fcb8b 3.999699481000 1100447 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": 659744, "vin": [ { "gen": { "height": 659734 } } ], "vout": [ { "amount": 3999699481, "target": { "key": "fdaaed22bc3442ff015755becfd71ddb5a7f4e2f296f5ffa4aae3ae6347fcb8b" } } ], "extra": [ 1, 175, 79, 168, 210, 230, 204, 180, 130, 1, 225, 171, 127, 108, 251, 70, 118, 110, 219, 153, 213, 197, 242, 57, 238, 254, 113, 108, 246, 243, 190, 65, 92, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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