Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392e26ec7172a67e53d38964ffd02e221a19b86839972bbbed6e9fcf1f697310

Tx prefix hash: 30e2216c89d78cca95a4e986bf6cbc5f33ffc1bb778aaba189e6f8dd2f2ed799
Tx public key: 33193fdd5916bc52b4956b1a9f74bdb2c0d4174e9c44e2ea850c862854d61fce
Timestamp: 1726312509 Timestamp [UCT]: 2024-09-14 11:15:09 Age [y:d:h:m:s]: 00:208:14:41:13
Block: 1109887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148928 RingCT/type: yes/0
Extra: 0133193fdd5916bc52b4956b1a9f74bdb2c0d4174e9c44e2ea850c862854d61fce021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4933a9cc4ba461fa33fef4cd0c8baead3a6b69ef555d31be69857cc8bb1fb3e3 0.600000000000 1588298 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": 1109897, "vin": [ { "gen": { "height": 1109887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4933a9cc4ba461fa33fef4cd0c8baead3a6b69ef555d31be69857cc8bb1fb3e3" } } ], "extra": [ 1, 51, 25, 63, 221, 89, 22, 188, 82, 180, 149, 107, 26, 159, 116, 189, 178, 192, 212, 23, 78, 156, 68, 226, 234, 133, 12, 134, 40, 84, 214, 31, 206, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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