Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35fdb501b708c76eaf84778a3dd8c42c28792d33d5eee62e3fe08debe5ce43d5

Tx prefix hash: d9d4566a58391309a276a0dedf5e08a2a61952cf8af1b9d40c5bba34e36ad6b3
Tx public key: a682d8ae1cc4b58e9af132b96f2c0c474266c3576a12b2aa6b26b3df579f7bb6
Timestamp: 1577385029 Timestamp [UCT]: 2019-12-26 18:30:29 Age [y:d:h:m:s]: 05:071:12:33:24
Block: 32389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200831 RingCT/type: yes/0
Extra: 01a682d8ae1cc4b58e9af132b96f2c0c474266c3576a12b2aa6b26b3df579f7bb60211000000b4398c17aa000000000000000000

1 output(s) for total of 479.383030421000 dcy

stealth address amount amount idx
00: f1e4af18ecb40e1bbbe181e68218a1fbd87a6cffc843303c09b4816c5380aafa 479.383030421000 53846 of 0

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": 32399, "vin": [ { "gen": { "height": 32389 } } ], "vout": [ { "amount": 479383030421, "target": { "key": "f1e4af18ecb40e1bbbe181e68218a1fbd87a6cffc843303c09b4816c5380aafa" } } ], "extra": [ 1, 166, 130, 216, 174, 28, 196, 181, 142, 154, 241, 50, 185, 111, 44, 12, 71, 66, 102, 195, 87, 106, 18, 178, 170, 107, 38, 179, 223, 87, 159, 123, 182, 2, 17, 0, 0, 0, 180, 57, 140, 23, 170, 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