Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75ca26589cc6ef8a4a92b2762c7dce14a6125e979889e8336b3d7bbc33840d9

Tx prefix hash: f74a4264c349307986e45031e2c315c6e295c8e3940fdd7c4c310233356daf74
Tx public key: b570ebfb4527efcc12b8e416d150e5ed751125d0f4239aa2b9c0803220b7e910
Timestamp: 1717417424 Timestamp [UCT]: 2024-06-03 12:23:44 Age [y:d:h:m:s]: 00:346:04:54:18
Block: 1036157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247439 RingCT/type: yes/0
Extra: 01b570ebfb4527efcc12b8e416d150e5ed751125d0f4239aa2b9c0803220b7e9100211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d02e72f3b955c06e340dd2c74ae9b8cc690248ba9a88e8d1ea88d05a647b15 0.600000000000 1504682 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": 1036167, "vin": [ { "gen": { "height": 1036157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d02e72f3b955c06e340dd2c74ae9b8cc690248ba9a88e8d1ea88d05a647b15" } } ], "extra": [ 1, 181, 112, 235, 251, 69, 39, 239, 204, 18, 184, 228, 22, 209, 80, 229, 237, 117, 17, 37, 208, 244, 35, 154, 162, 185, 192, 128, 50, 32, 183, 233, 16, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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