Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339ab7b8407e0cf9bbc33b4562f77a8d771be9e54f803e3fdb74c8756a177816

Tx prefix hash: 27e7586128a98e7574defa7a6cf8fc401cf5c348d21bb0679643fbc81f0e121c
Tx public key: 52efb2343ec488ccde9d83b21e143251f14c6edbccc4b317a5cf6d45dce7c4e6
Timestamp: 1672712390 Timestamp [UCT]: 2023-01-03 02:19:50 Age [y:d:h:m:s]: 02:338:00:32:57
Block: 666383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761016 RingCT/type: yes/0
Extra: 0152efb2343ec488ccde9d83b21e143251f14c6edbccc4b317a5cf6d45dce7c4e602110000000152542ceb000000000000000000

1 output(s) for total of 3.801862928000 dcy

stealth address amount amount idx
00: 15850fa52a89ed13d987875681becff4a2243168ca73ea2063d7ae472f89cbf6 3.801862928000 1107492 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": 666393, "vin": [ { "gen": { "height": 666383 } } ], "vout": [ { "amount": 3801862928, "target": { "key": "15850fa52a89ed13d987875681becff4a2243168ca73ea2063d7ae472f89cbf6" } } ], "extra": [ 1, 82, 239, 178, 52, 62, 196, 136, 204, 222, 157, 131, 178, 30, 20, 50, 81, 241, 76, 110, 219, 204, 196, 179, 23, 165, 207, 109, 69, 220, 231, 196, 230, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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