Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597811a8bf18c6248c3c265fee055f9150d8e9779491b9ea50639e5c87d83dfd

Tx prefix hash: 696c93fe901be91bd5d8b83492a8d9e740597c956e6d2566fbc30fc0a5529057
Tx public key: c10ae6358abf2d292245747e6cbc595e7e46de4ddee4ceeaa135c91b41a68e59
Timestamp: 1735719255 Timestamp [UCT]: 2025-01-01 08:14:15 Age [y:d:h:m:s]: 00:098:22:32:54
Block: 1187740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70509 RingCT/type: yes/0
Extra: 01c10ae6358abf2d292245747e6cbc595e7e46de4ddee4ceeaa135c91b41a68e59021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8881796d6304f5179cf418ea56d7c3eaf2f3a451186dd28bc895d57e1a8f4502 0.600000000000 1674235 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": 1187750, "vin": [ { "gen": { "height": 1187740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8881796d6304f5179cf418ea56d7c3eaf2f3a451186dd28bc895d57e1a8f4502" } } ], "extra": [ 1, 193, 10, 230, 53, 138, 191, 45, 41, 34, 69, 116, 126, 108, 188, 89, 94, 126, 70, 222, 77, 222, 228, 206, 234, 161, 53, 201, 27, 65, 166, 142, 89, 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