Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ace7e3dc642a67f781d6085f823887a037a4d7c4f12df92020cf2b21109e289d

Tx prefix hash: 3f266464d1d4c018d6c377c4c6221b0d0a90f433bcd20316445fb0bbc4bba181
Tx public key: 439e55f47e7b0d8f9fbc2f30f540fa938e1c70dd1cfa0c27388748a031bd0bb2
Timestamp: 1719971069 Timestamp [UCT]: 2024-07-03 01:44:29 Age [y:d:h:m:s]: 00:275:00:19:47
Block: 1057309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196495 RingCT/type: yes/0
Extra: 01439e55f47e7b0d8f9fbc2f30f540fa938e1c70dd1cfa0c27388748a031bd0bb20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3c36a487bcbc9be611b0ab7e6a4205579a57505cae21f5e0d8fc7eecbf0ca9 0.600000000000 1527744 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": 1057319, "vin": [ { "gen": { "height": 1057309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3c36a487bcbc9be611b0ab7e6a4205579a57505cae21f5e0d8fc7eecbf0ca9" } } ], "extra": [ 1, 67, 158, 85, 244, 126, 123, 13, 143, 159, 188, 47, 48, 245, 64, 250, 147, 142, 28, 112, 221, 28, 250, 12, 39, 56, 135, 72, 160, 49, 189, 11, 178, 2, 17, 0, 0, 0, 5, 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