Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34fac94c9779c85933a768d223b6935273ced922c798e4df6f19ea7196c708d

Tx prefix hash: ad18dcb285eecb70ba73866c8611375b2a28cccd5dd36922d187d4bd1c4533a3
Tx public key: b40e32e6148a8f0a2ebd4cf8aa819f68b4c8c386787427d2fd4fa2459e4daac0
Timestamp: 1733083117 Timestamp [UCT]: 2024-12-01 19:58:37 Age [y:d:h:m:s]: 00:113:04:20:24
Block: 1165929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80677 RingCT/type: yes/0
Extra: 01b40e32e6148a8f0a2ebd4cf8aa819f68b4c8c386787427d2fd4fa2459e4daac002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7546a758f781abb25801bbb44510c16c343f109062990af2bde98da9087c07 0.600000000000 1651604 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": 1165939, "vin": [ { "gen": { "height": 1165929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7546a758f781abb25801bbb44510c16c343f109062990af2bde98da9087c07" } } ], "extra": [ 1, 180, 14, 50, 230, 20, 138, 143, 10, 46, 189, 76, 248, 170, 129, 159, 104, 180, 200, 195, 134, 120, 116, 39, 210, 253, 79, 162, 69, 158, 77, 170, 192, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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