Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad345632823c793e1c5f88c74c1758d7e6a2a0c919b284b5187a0e37edf64ac

Tx prefix hash: c75773e9f8f7d0dc4a0c2386e7cc4e7c7fecff645fa6d6981e33a2b468249102
Tx public key: 133f93da45fd22f037af0ffe7059981f5cd278e77a5e478f762baa9f3d9b92eb
Timestamp: 1583631773 Timestamp [UCT]: 2020-03-08 01:42:53 Age [y:d:h:m:s]: 05:238:20:36:48
Block: 78240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1323977 RingCT/type: yes/0
Extra: 01133f93da45fd22f037af0ffe7059981f5cd278e77a5e478f762baa9f3d9b92eb02110000001be89b4e54000000000000000000

1 output(s) for total of 337.877438878000 dcy

stealth address amount amount idx
00: e87f6e275fa7e50f1014de922ba7330ca1d56708a4e8fd11041a9f2f1b18ac66 337.877438878000 143684 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": 78250, "vin": [ { "gen": { "height": 78240 } } ], "vout": [ { "amount": 337877438878, "target": { "key": "e87f6e275fa7e50f1014de922ba7330ca1d56708a4e8fd11041a9f2f1b18ac66" } } ], "extra": [ 1, 19, 63, 147, 218, 69, 253, 34, 240, 55, 175, 15, 254, 112, 89, 152, 31, 92, 210, 120, 231, 122, 94, 71, 143, 118, 43, 170, 159, 61, 155, 146, 235, 2, 17, 0, 0, 0, 27, 232, 155, 78, 84, 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