Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea01cb613154c2063ca71cf0f82476499ce22bcb81c3f55ab750ec037cdfdae

Tx prefix hash: f8739b985118d2a6e276faebd3fa3ffa6277c8ef600b4b414e54a313c49cb745
Tx public key: 483f2b19774b1d962cb61af2f4edb0b35264028b81b58d4ca97da298c3cd1464
Timestamp: 1724049651 Timestamp [UCT]: 2024-08-19 06:40:51 Age [y:d:h:m:s]: 00:221:17:38:10
Block: 1091134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158342 RingCT/type: yes/0
Extra: 01483f2b19774b1d962cb61af2f4edb0b35264028b81b58d4ca97da298c3cd1464021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ea21e68c6c338654dbbca13bcc55d8e04663af0cd648c5990e209793cb0d03 0.600000000000 1565763 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": 1091144, "vin": [ { "gen": { "height": 1091134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ea21e68c6c338654dbbca13bcc55d8e04663af0cd648c5990e209793cb0d03" } } ], "extra": [ 1, 72, 63, 43, 25, 119, 75, 29, 150, 44, 182, 26, 242, 244, 237, 176, 179, 82, 100, 2, 139, 129, 181, 141, 76, 169, 125, 162, 152, 195, 205, 20, 100, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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