Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c065603fbf80d500d34285aeea13e9f9f9d7f18245ba8c9e76a2e755b5693833

Tx prefix hash: c586d964f1b53df486df05c73606e0267032fec5a3b9254f8befd48e1c96d4cd
Tx public key: 71a977c0665167e2d0382b371bbbf7e245008e4637e98cd20014e0c8b08eaa95
Timestamp: 1714643078 Timestamp [UCT]: 2024-05-02 09:44:38 Age [y:d:h:m:s]: 01:191:05:59:35
Block: 1013150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395310 RingCT/type: yes/0
Extra: 0171a977c0665167e2d0382b371bbbf7e245008e4637e98cd20014e0c8b08eaa950211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0368edfe0c2e3c8c179cf73e3d17770123d523ebd49068d15aa6b66e50bd6797 0.600000000000 1475889 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": 1013160, "vin": [ { "gen": { "height": 1013150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0368edfe0c2e3c8c179cf73e3d17770123d523ebd49068d15aa6b66e50bd6797" } } ], "extra": [ 1, 113, 169, 119, 192, 102, 81, 103, 226, 208, 56, 43, 55, 27, 187, 247, 226, 69, 0, 142, 70, 55, 233, 140, 210, 0, 20, 224, 200, 176, 142, 170, 149, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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