Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733a06353ff058b8cce357eed07217598625d6989d35e70681c920f6039a914f

Tx prefix hash: 449aab5f879a97e1157e89099e4ccf8fb60cee21369d4df02244e1bd77f72ff3
Tx public key: 91414a56070af9b6ae875a71dd2e03e5929c6a48572e6040387088b5a2f34d62
Timestamp: 1688210801 Timestamp [UCT]: 2023-07-01 11:26:41 Age [y:d:h:m:s]: 01:198:17:50:18
Block: 794265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403397 RingCT/type: yes/0
Extra: 0191414a56070af9b6ae875a71dd2e03e5929c6a48572e6040387088b5a2f34d6202110000000675e3f0e9000000000000000000

1 output(s) for total of 1.433080142000 dcy

stealth address amount amount idx
00: a4fd953956d2b9ed8a3a65a924c277f50c6926518c9a8a178c16ac22f408ab37 1.433080142000 1244998 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": 794275, "vin": [ { "gen": { "height": 794265 } } ], "vout": [ { "amount": 1433080142, "target": { "key": "a4fd953956d2b9ed8a3a65a924c277f50c6926518c9a8a178c16ac22f408ab37" } } ], "extra": [ 1, 145, 65, 74, 86, 7, 10, 249, 182, 174, 135, 90, 113, 221, 46, 3, 229, 146, 156, 106, 72, 87, 46, 96, 64, 56, 112, 136, 181, 162, 243, 77, 98, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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