Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ac550352c14526ffa94835d1c8556c752346fe30509d3d86f57452d0f7ef53

Tx prefix hash: 742dca8cb21febf3351fc51215a2f9e7413ab1990d69c8cf26368c60c740e341
Tx public key: f9d4e7a517e1b64eab8c215b36337e4b51fa99acf90fc314dbfac856a5d1fa0c
Timestamp: 1720229305 Timestamp [UCT]: 2024-07-06 01:28:25 Age [y:d:h:m:s]: 00:208:17:07:22
Block: 1059445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149090 RingCT/type: yes/0
Extra: 01f9d4e7a517e1b64eab8c215b36337e4b51fa99acf90fc314dbfac856a5d1fa0c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c9ab772faa69386f1be3b4bccdbc0af0862900aafbee11d0b0489be3e9fe09 0.600000000000 1529914 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": 1059455, "vin": [ { "gen": { "height": 1059445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c9ab772faa69386f1be3b4bccdbc0af0862900aafbee11d0b0489be3e9fe09" } } ], "extra": [ 1, 249, 212, 231, 165, 23, 225, 182, 78, 171, 140, 33, 91, 54, 51, 126, 75, 81, 250, 153, 172, 249, 15, 195, 20, 219, 250, 200, 86, 165, 209, 250, 12, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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