Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d88d77d006520279c42b911cb6c21f4211cbdb317675d5da8ef2b54b9a04e3b

Tx prefix hash: 77f934c33404116d01e60468e75078ccea2535f1af5788273497338861f421d9
Tx public key: c3b0bf535d1560a985569672c1c7803ba32715b526bbe95f2683c52b75a919c6
Timestamp: 1708886513 Timestamp [UCT]: 2024-02-25 18:41:53 Age [y:d:h:m:s]: 01:045:13:51:36
Block: 965429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293589 RingCT/type: yes/0
Extra: 01c3b0bf535d1560a985569672c1c7803ba32715b526bbe95f2683c52b75a919c602110000001d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0654c64c6408326d8e28a4d9fc06a42786cb03f5c3aa3a360c94d3c357b3f8b 0.600000000000 1425180 of 15

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": 965439, "vin": [ { "gen": { "height": 965429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0654c64c6408326d8e28a4d9fc06a42786cb03f5c3aa3a360c94d3c357b3f8b" } } ], "extra": [ 1, 195, 176, 191, 83, 93, 21, 96, 169, 133, 86, 150, 114, 193, 199, 128, 59, 163, 39, 21, 181, 38, 187, 233, 95, 38, 131, 197, 43, 117, 169, 25, 198, 2, 17, 0, 0, 0, 29, 122, 156, 244, 199, 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