Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27d3505f60fce0a4e3042e1d7abf827726e1b8119d1ca719b2ab7eb19442b1ea

Tx prefix hash: f9a755e4890440cb74c1dc63f0894fd54b1fb4855989365205b0fff52b17dc87
Tx public key: 0f14e7f931b3e8d6fee6ca84c9041eb478f2f9f08089de35f0158c96d93d79a9
Timestamp: 1702916633 Timestamp [UCT]: 2023-12-18 16:23:53 Age [y:d:h:m:s]: 01:149:05:55:07
Block: 915930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367806 RingCT/type: yes/0
Extra: 010f14e7f931b3e8d6fee6ca84c9041eb478f2f9f08089de35f0158c96d93d79a902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de5e99588fea4d8abe6ff9381efbf600a0c1a1f53dd915793900d3d0680e654f 0.600000000000 1373364 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": 915940, "vin": [ { "gen": { "height": 915930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de5e99588fea4d8abe6ff9381efbf600a0c1a1f53dd915793900d3d0680e654f" } } ], "extra": [ 1, 15, 20, 231, 249, 49, 179, 232, 214, 254, 230, 202, 132, 201, 4, 30, 180, 120, 242, 249, 240, 128, 137, 222, 53, 240, 21, 140, 150, 217, 61, 121, 169, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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