Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4434d2423d55dbb2dd9a1c5cc543c09e675cb3871ee8e0e9f7208aa1614a47e9

Tx prefix hash: f58eb9c0376714973ca4ad0c3ca1f4c96cd7d65fd9dc4d834f51792756b8f9f2
Tx public key: a39423856b5d07bfdcb87ea113ae8596e617abf14e02a1954d81008485aa5651
Timestamp: 1714591719 Timestamp [UCT]: 2024-05-01 19:28:39 Age [y:d:h:m:s]: 00:206:18:34:33
Block: 1012721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148014 RingCT/type: yes/0
Extra: 01a39423856b5d07bfdcb87ea113ae8596e617abf14e02a1954d81008485aa56510211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6c0de9832b2eea2aadd7d3427f73fc71d649363f4efcff60b88674a8622b919 0.600000000000 1475333 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": 1012731, "vin": [ { "gen": { "height": 1012721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6c0de9832b2eea2aadd7d3427f73fc71d649363f4efcff60b88674a8622b919" } } ], "extra": [ 1, 163, 148, 35, 133, 107, 93, 7, 191, 220, 184, 126, 161, 19, 174, 133, 150, 230, 23, 171, 241, 78, 2, 161, 149, 77, 129, 0, 132, 133, 170, 86, 81, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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