Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579c73250ad4f7a0267fa1c0ffb7d9179d63744503235bf1fe07d00f740fd894

Tx prefix hash: f642824b8dcc333062a4d3d6c75d6d6eafcae95f1e73a84f1afacd6fd02532e6
Tx public key: d13f85e426a4b9dc74e865707e448c7b5333a2a13a3dc9d2bfb38003268d6b69
Timestamp: 1717313285 Timestamp [UCT]: 2024-06-02 07:28:05 Age [y:d:h:m:s]: 01:005:23:37:44
Block: 1035292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265175 RingCT/type: yes/0
Extra: 01d13f85e426a4b9dc74e865707e448c7b5333a2a13a3dc9d2bfb38003268d6b6902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ce9db393145b7b668613bc1fb71f5afe2c7789877f2c1cbdaa2827d2bbdeb2a 0.600000000000 1503813 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": 1035302, "vin": [ { "gen": { "height": 1035292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ce9db393145b7b668613bc1fb71f5afe2c7789877f2c1cbdaa2827d2bbdeb2a" } } ], "extra": [ 1, 209, 63, 133, 228, 38, 164, 185, 220, 116, 232, 101, 112, 126, 68, 140, 123, 83, 51, 162, 161, 58, 61, 201, 210, 191, 179, 128, 3, 38, 141, 107, 105, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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