Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3daedc3f92fc95480573fb824f11e7a5a7e35137e3ff761a9b48074595e023aa

Tx prefix hash: e7bfb5d3a34e7adeec71564f35f3eecafb06cad54c7b285b5263689f93541418
Tx public key: a7eb5199a4ac8fb80a73a686d6fcbe4d4d7c25bbb7c8233a0cc9e37ce174d41b
Timestamp: 1739347150 Timestamp [UCT]: 2025-02-12 07:59:10 Age [y:d:h:m:s]: 00:238:19:38:06
Block: 1217519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168385 RingCT/type: yes/0
Extra: 01a7eb5199a4ac8fb80a73a686d6fcbe4d4d7c25bbb7c8233a0cc9e37ce174d41b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 123c9a101e8f2b24ccdd07f68a33668d3cd0eb049d7407528e0e190afa53940f 0.600000000000 1704332 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": 1217529, "vin": [ { "gen": { "height": 1217519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "123c9a101e8f2b24ccdd07f68a33668d3cd0eb049d7407528e0e190afa53940f" } } ], "extra": [ 1, 167, 235, 81, 153, 164, 172, 143, 184, 10, 115, 166, 134, 214, 252, 190, 77, 77, 124, 37, 187, 183, 200, 35, 58, 12, 201, 227, 124, 225, 116, 212, 27, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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