Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656199364147f798193a1a9e101165823fcd5cccf240c1971b4499a51b1530be

Tx prefix hash: dbcf25ef9471c1f7ff384e8eb9fb9f845e98c5ff8a65ae87f58155d1d2ecd650
Tx public key: ae6516d957f5dd3584e07ca786df6a788c0db8b478b8a03ce3b207237622a733
Timestamp: 1704595543 Timestamp [UCT]: 2024-01-07 02:45:43 Age [y:d:h:m:s]: 01:307:03:04:09
Block: 929820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478343 RingCT/type: yes/0
Extra: 01ae6516d957f5dd3584e07ca786df6a788c0db8b478b8a03ce3b207237622a7330211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad02a02fa101a5e6c6c421b3d4f65a1fbeae3e8e859edaaabb55fcb22b1a7562 0.600000000000 1387696 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": 929830, "vin": [ { "gen": { "height": 929820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad02a02fa101a5e6c6c421b3d4f65a1fbeae3e8e859edaaabb55fcb22b1a7562" } } ], "extra": [ 1, 174, 101, 22, 217, 87, 245, 221, 53, 132, 224, 124, 167, 134, 223, 106, 120, 140, 13, 184, 180, 120, 184, 160, 60, 227, 178, 7, 35, 118, 34, 167, 51, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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