Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 284c7be78fab3985854c908fd63d1a5a88e02607694d41ae1752b40da8b7e180

Tx prefix hash: f227c48bc0650e9cc6a6589d4e46ebd5dcaf37fc84914d49d82588c5fb0e9b7e
Tx public key: 571c210f8d599d0d9f7b1e19a2f70ae8ba3e4cbf24dab860b36761a70fab087b
Timestamp: 1717192782 Timestamp [UCT]: 2024-05-31 21:59:42 Age [y:d:h:m:s]: 00:304:03:33:00
Block: 1034286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217360 RingCT/type: yes/0
Extra: 01571c210f8d599d0d9f7b1e19a2f70ae8ba3e4cbf24dab860b36761a70fab087b02110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde3deef14695970e3a14ee0946d645a6ac516bbb0c391b1bed811b8aa15d52a 0.600000000000 1502787 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": 1034296, "vin": [ { "gen": { "height": 1034286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde3deef14695970e3a14ee0946d645a6ac516bbb0c391b1bed811b8aa15d52a" } } ], "extra": [ 1, 87, 28, 33, 15, 141, 89, 157, 13, 159, 123, 30, 25, 162, 247, 10, 232, 186, 62, 76, 191, 36, 218, 184, 96, 179, 103, 97, 167, 15, 171, 8, 123, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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