Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344acd215d6e1e2f48f93b1d085f1d4d6575aedd467aecb1380e06e31b8ba760

Tx prefix hash: 8196cdec29150dbbf853d32be3ecff86b022af176405dc41a39a298c78c0ee29
Tx public key: e166894335a64f221c7606910cce82077ef4d65bc5d284b8c45e92c8cf30c6ee
Timestamp: 1699720344 Timestamp [UCT]: 2023-11-11 16:32:24 Age [y:d:h:m:s]: 01:072:12:05:34
Block: 889434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313182 RingCT/type: yes/0
Extra: 01e166894335a64f221c7606910cce82077ef4d65bc5d284b8c45e92c8cf30c6ee02110000000833af99f4000000000000000000

1 output(s) for total of 0.693323523000 dcy

stealth address amount amount idx
00: d6465f40677a558ea4fd8ce62a48e8210ec72548d8e77aa412a64aff398ec4fc 0.693323523000 1345431 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": 889444, "vin": [ { "gen": { "height": 889434 } } ], "vout": [ { "amount": 693323523, "target": { "key": "d6465f40677a558ea4fd8ce62a48e8210ec72548d8e77aa412a64aff398ec4fc" } } ], "extra": [ 1, 225, 102, 137, 67, 53, 166, 79, 34, 28, 118, 6, 145, 12, 206, 130, 7, 126, 244, 214, 91, 197, 210, 132, 184, 196, 94, 146, 200, 207, 48, 198, 238, 2, 17, 0, 0, 0, 8, 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