Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fabd927845dfadcb563589f8d4e87e1888676f7a77741647c3e3760a30c3af22

Tx prefix hash: f4a61641152bf1ae296546e90e7c57c7ee03ce0869a393ce8260f9843a54ba77
Tx public key: f4c3c247de0516746b12394681a89ca91120fda90ffe18b2b1ac1b86d6cf27b6
Timestamp: 1694873752 Timestamp [UCT]: 2023-09-16 14:15:52 Age [y:d:h:m:s]: 01:250:03:22:09
Block: 849428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439905 RingCT/type: yes/0
Extra: 01f4c3c247de0516746b12394681a89ca91120fda90ffe18b2b1ac1b86d6cf27b602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.940789538000 dcy

stealth address amount amount idx
00: 38c73762f61d8e1c861a5a22c6d84e5fda6593729bf8a4d32854fc6d9d00ef8e 0.940789538000 1303094 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": 849438, "vin": [ { "gen": { "height": 849428 } } ], "vout": [ { "amount": 940789538, "target": { "key": "38c73762f61d8e1c861a5a22c6d84e5fda6593729bf8a4d32854fc6d9d00ef8e" } } ], "extra": [ 1, 244, 195, 194, 71, 222, 5, 22, 116, 107, 18, 57, 70, 129, 168, 156, 169, 17, 32, 253, 169, 15, 254, 24, 178, 177, 172, 27, 134, 214, 207, 39, 182, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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