Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21589900cd704b756970e08bbf4c6dba1901956931b18433086139b7a52e1d2e

Tx prefix hash: 0acc108be46baa37c88a80a99a8895e5925baea996eed65c5e6814a069eadf65
Tx public key: 3d6381785de8edc7c9e3cf426b2830fdc890cda023065c8b33cecc418cbb28a8
Timestamp: 1706609595 Timestamp [UCT]: 2024-01-30 10:13:15 Age [y:d:h:m:s]: 01:307:16:47:23
Block: 946527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478743 RingCT/type: yes/0
Extra: 013d6381785de8edc7c9e3cf426b2830fdc890cda023065c8b33cecc418cbb28a80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8a34f56f1f9e76f53411af388f62f4449c21dc31a8ce1e6e6576064968d2e5c 0.600000000000 1404859 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": 946537, "vin": [ { "gen": { "height": 946527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8a34f56f1f9e76f53411af388f62f4449c21dc31a8ce1e6e6576064968d2e5c" } } ], "extra": [ 1, 61, 99, 129, 120, 93, 232, 237, 199, 201, 227, 207, 66, 107, 40, 48, 253, 200, 144, 205, 160, 35, 6, 92, 139, 51, 206, 204, 65, 140, 187, 40, 168, 2, 17, 0, 0, 0, 5, 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