Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59718ea96c27fbaaf3a4a3d8df28f7709581a5b580c7cb9a1ebce040db669b4e

Tx prefix hash: 53ee72c6a46fa8f1ebe1de089fa6942608b0efb827ea3cde24fb46f19d1d8e2f
Tx public key: 30c5836a96ad3e7e4bcc8f7eff28824531b829361ab8e35c67d801ceeca6a49a
Timestamp: 1715342806 Timestamp [UCT]: 2024-05-10 12:06:46 Age [y:d:h:m:s]: 01:181:22:33:14
Block: 1018953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388639 RingCT/type: yes/0
Extra: 0130c5836a96ad3e7e4bcc8f7eff28824531b829361ab8e35c67d801ceeca6a49a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f0e9fc7a709639947ec9b2a3f3c6c04decf22e1d4d674fc90e2ba904dccef4 0.600000000000 1482782 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": 1018963, "vin": [ { "gen": { "height": 1018953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f0e9fc7a709639947ec9b2a3f3c6c04decf22e1d4d674fc90e2ba904dccef4" } } ], "extra": [ 1, 48, 197, 131, 106, 150, 173, 62, 126, 75, 204, 143, 126, 255, 40, 130, 69, 49, 184, 41, 54, 26, 184, 227, 92, 103, 216, 1, 206, 236, 166, 164, 154, 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