Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 952c0bb89f53843fdd2eacd3dcafb0101bd9356ea2a3c5dc9438b521e0d81ac5

Tx prefix hash: 3923456e3cf79cf6666de67fb1746c144b2f12ed4b6e1bd8d8c90f932842c7bd
Tx public key: d948c9e4c489babdb06a70f86eefc93786bfc2ca6a35d036610198ca43ff0922
Timestamp: 1674792453 Timestamp [UCT]: 2023-01-27 04:07:33 Age [y:d:h:m:s]: 02:077:02:18:56
Block: 683645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576732 RingCT/type: yes/0
Extra: 01d948c9e4c489babdb06a70f86eefc93786bfc2ca6a35d036610198ca43ff09220211000000035029cbac000000000000000000

1 output(s) for total of 3.332730973000 dcy

stealth address amount amount idx
00: e9a21556b4ce64a4b5da1251473343420f21a75138db3ef8520ebc3a0df1f1de 3.332730973000 1125840 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": 683655, "vin": [ { "gen": { "height": 683645 } } ], "vout": [ { "amount": 3332730973, "target": { "key": "e9a21556b4ce64a4b5da1251473343420f21a75138db3ef8520ebc3a0df1f1de" } } ], "extra": [ 1, 217, 72, 201, 228, 196, 137, 186, 189, 176, 106, 112, 248, 110, 239, 201, 55, 134, 191, 194, 202, 106, 53, 208, 54, 97, 1, 152, 202, 67, 255, 9, 34, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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