Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c7f333965ab58d3529ab8413a8b9b2f48118ace8f8c2ce5b25f5c44c798447a

Tx prefix hash: a75980a337d085e3e6e0265a93115ff900c855ba0f9a918ee0c5ab9683470d9a
Tx public key: e964bab35df4e5b8f2a575e9f308d48b2a41dc63b45f89c0df6588555057df0f
Timestamp: 1625887877 Timestamp [UCT]: 2021-07-10 03:31:17 Age [y:d:h:m:s]: 04:117:21:05:48
Block: 291183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113242 RingCT/type: yes/0
Extra: 01e964bab35df4e5b8f2a575e9f308d48b2a41dc63b45f89c0df6588555057df0f02110000001a9cd60737000000000000000000

1 output(s) for total of 66.556480524000 dcy

stealth address amount amount idx
00: 63084ee8ae1349c23e27472889f1fabf130c30360df03ace8a0c28adc39820f3 66.556480524000 609775 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": 291193, "vin": [ { "gen": { "height": 291183 } } ], "vout": [ { "amount": 66556480524, "target": { "key": "63084ee8ae1349c23e27472889f1fabf130c30360df03ace8a0c28adc39820f3" } } ], "extra": [ 1, 233, 100, 186, 179, 93, 244, 229, 184, 242, 165, 117, 233, 243, 8, 212, 139, 42, 65, 220, 99, 180, 95, 137, 192, 223, 101, 136, 85, 80, 87, 223, 15, 2, 17, 0, 0, 0, 26, 156, 214, 7, 55, 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