Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8166f57e1677d9d8eadbc3c85c35c6dfbfb627543a472aa8b143bc23c99d7133

Tx prefix hash: 757ccb7032f3e0b2534e63723563a10f5f73f96fad257effb349266c744cb084
Tx public key: 2ca6968499b8b38e8df13dd13733e6fc3097d46d9e6f362c57aaafb3a4276228
Timestamp: 1738527644 Timestamp [UCT]: 2025-02-02 20:20:44 Age [y:d:h:m:s]: 00:291:01:39:33
Block: 1210721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205797 RingCT/type: yes/0
Extra: 012ca6968499b8b38e8df13dd13733e6fc3097d46d9e6f362c57aaafb3a4276228021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a38ac0fa4249a06792eedb7411b082052f27237d5dda590d43bb6b5f3f4e220 0.600000000000 1697476 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": 1210731, "vin": [ { "gen": { "height": 1210721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a38ac0fa4249a06792eedb7411b082052f27237d5dda590d43bb6b5f3f4e220" } } ], "extra": [ 1, 44, 166, 150, 132, 153, 184, 179, 142, 141, 241, 61, 209, 55, 51, 230, 252, 48, 151, 212, 109, 158, 111, 54, 44, 87, 170, 175, 179, 164, 39, 98, 40, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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