Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1267e6665c8bfed40f414a44c348199e7f44eb39d0f7bc90e5720fce51c725

Tx prefix hash: 8072c6d5bcd4964ad535a01819daedf2d42fc6535656c17cd1cccdd06d28d67e
Tx public key: 3c4f5719167c56c7236857bf04b01eee9727c38ca61736feb5c2a95d84192a77
Timestamp: 1583238315 Timestamp [UCT]: 2020-03-03 12:25:15 Age [y:d:h:m:s]: 04:216:17:02:04
Block: 75584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1049169 RingCT/type: yes/0
Extra: 013c4f5719167c56c7236857bf04b01eee9727c38ca61736feb5c2a95d84192a77021100000134c71d3ff9000000000000000000

1 output(s) for total of 344.793943034000 dcy

stealth address amount amount idx
00: b64773a8afae859f4b608df2aacf079068ab47ec809e75c9258f9b57e84406d8 344.793943034000 139538 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": 75594, "vin": [ { "gen": { "height": 75584 } } ], "vout": [ { "amount": 344793943034, "target": { "key": "b64773a8afae859f4b608df2aacf079068ab47ec809e75c9258f9b57e84406d8" } } ], "extra": [ 1, 60, 79, 87, 25, 22, 124, 86, 199, 35, 104, 87, 191, 4, 176, 30, 238, 151, 39, 195, 140, 166, 23, 54, 254, 181, 194, 169, 93, 132, 25, 42, 119, 2, 17, 0, 0, 1, 52, 199, 29, 63, 249, 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