Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731d1718ef979beea0a49d6e295c94cf1c6995feb4377d230be991f216fe1040

Tx prefix hash: 571aa0d0e45e0f97fca15fa1243da06a598ec9a6ba5a7ae473c07b4e2dcc6aff
Tx public key: 0d773493aa1d0b68191b9f6cb203526efa6c767668efe9f23d44290a39b9fdda
Timestamp: 1727502831 Timestamp [UCT]: 2024-09-28 05:53:51 Age [y:d:h:m:s]: 00:187:20:10:43
Block: 1119763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134042 RingCT/type: yes/0
Extra: 010d773493aa1d0b68191b9f6cb203526efa6c767668efe9f23d44290a39b9fdda02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f5aa3795790b4ec7a7cddb9454809d30d8ae87ff4311a7e233732be9bb593e2 0.600000000000 1601436 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": 1119773, "vin": [ { "gen": { "height": 1119763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f5aa3795790b4ec7a7cddb9454809d30d8ae87ff4311a7e233732be9bb593e2" } } ], "extra": [ 1, 13, 119, 52, 147, 170, 29, 11, 104, 25, 27, 159, 108, 178, 3, 82, 110, 250, 108, 118, 118, 104, 239, 233, 242, 61, 68, 41, 10, 57, 185, 253, 218, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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