Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f41498bea5e7fcd53fb0beb59ed3451b0e8c96490e1456700cf1b5c88c606afb

Tx prefix hash: 714b2804c1113fe5ccb713f25e9eca2bafb6c6a4e73f1dc2b9f9df2ac6c7a474
Tx public key: 6cf240bde3207fa8bdfb14fef16815ddb6c0abacb5c799272786b627bfbad6f3
Timestamp: 1707457525 Timestamp [UCT]: 2024-02-09 05:45:25 Age [y:d:h:m:s]: 01:061:01:06:42
Block: 953564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304688 RingCT/type: yes/0
Extra: 016cf240bde3207fa8bdfb14fef16815ddb6c0abacb5c799272786b627bfbad6f302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c4e8b855f01bf991789bb210f58676998f988458bb533ca8c0be2cb5105319 0.600000000000 1412792 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": 953574, "vin": [ { "gen": { "height": 953564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c4e8b855f01bf991789bb210f58676998f988458bb533ca8c0be2cb5105319" } } ], "extra": [ 1, 108, 242, 64, 189, 227, 32, 127, 168, 189, 251, 20, 254, 241, 104, 21, 221, 182, 192, 171, 172, 181, 199, 153, 39, 39, 134, 182, 39, 191, 186, 214, 243, 2, 17, 0, 0, 0, 4, 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