Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a67472606dcae562c492f439e47aab5d6f42e3f1cf80582ee6fd34ddd70c675

Tx prefix hash: a1dabd423282197d9f1218ca135100bb88306c8e981501ae86f3510aab8a3c53
Tx public key: 8aaa0c44c7a07c6ff572bbd09d60e7e51b2556cdb04c9807934f410cf4b923ca
Timestamp: 1726611410 Timestamp [UCT]: 2024-09-17 22:16:50 Age [y:d:h:m:s]: 01:054:01:02:00
Block: 1112356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297045 RingCT/type: yes/0
Extra: 018aaa0c44c7a07c6ff572bbd09d60e7e51b2556cdb04c9807934f410cf4b923ca02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 743309f00495e3f0f0fb929a6f79891e426c1608fb64379a8d2118db4acfb08a 0.600000000000 1591651 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": 1112366, "vin": [ { "gen": { "height": 1112356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "743309f00495e3f0f0fb929a6f79891e426c1608fb64379a8d2118db4acfb08a" } } ], "extra": [ 1, 138, 170, 12, 68, 199, 160, 124, 111, 245, 114, 187, 208, 157, 96, 231, 229, 27, 37, 86, 205, 176, 76, 152, 7, 147, 79, 65, 12, 244, 185, 35, 202, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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