Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2daff245c421e92f78ae90d23c8781a303aad2970f6d13543a3672ebd1750a7

Tx prefix hash: bc821c6d39849e049d7f556b583f541d2cc6df1f7ffc66065c256c9b79bb8eff
Tx public key: 53a61b112e274b954694dad77861453771743f73634bb6d8827e600e7b3e74de
Timestamp: 1721449616 Timestamp [UCT]: 2024-07-20 04:26:56 Age [y:d:h:m:s]: 00:096:12:04:04
Block: 1069610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69045 RingCT/type: yes/0
Extra: 0153a61b112e274b954694dad77861453771743f73634bb6d8827e600e7b3e74de021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b1e5339e86ea63e2ac1f5be7264b47b5ca3a4f3893a8bc2dffdc6cf40917010 0.600000000000 1541095 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": 1069620, "vin": [ { "gen": { "height": 1069610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b1e5339e86ea63e2ac1f5be7264b47b5ca3a4f3893a8bc2dffdc6cf40917010" } } ], "extra": [ 1, 83, 166, 27, 17, 46, 39, 75, 149, 70, 148, 218, 215, 120, 97, 69, 55, 113, 116, 63, 115, 99, 75, 182, 216, 130, 126, 96, 14, 123, 62, 116, 222, 2, 17, 0, 0, 0, 1, 22, 38, 19, 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