Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12f89e4dc68a0bf316ca63a8c65369a6edc3dba142e62b9c0b029ea2d6a2bf35

Tx prefix hash: f720f08b945d8d7f07ce56ed5ac82451dc3c097a5d6ba3bec482cfbf39842683
Tx public key: a62eb5cec8d5108ca0019e19bffa193d9d0c7dc596fa31169aca3c8e6f1a0aea
Timestamp: 1709833446 Timestamp [UCT]: 2024-03-07 17:44:06 Age [y:d:h:m:s]: 01:010:15:14:24
Block: 973279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268591 RingCT/type: yes/0
Extra: 01a62eb5cec8d5108ca0019e19bffa193d9d0c7dc596fa31169aca3c8e6f1a0aea02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ca4edd2afb4b122323315a495284ddcbc1069dbff81728110351882d2f4be0a 0.600000000000 1433214 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": 973289, "vin": [ { "gen": { "height": 973279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ca4edd2afb4b122323315a495284ddcbc1069dbff81728110351882d2f4be0a" } } ], "extra": [ 1, 166, 46, 181, 206, 200, 213, 16, 140, 160, 1, 158, 25, 191, 250, 25, 61, 157, 12, 125, 197, 150, 250, 49, 22, 154, 202, 60, 142, 111, 26, 10, 234, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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