Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dee98d2f577877798d8d03fa10c923e72de5d191397c8d6a406b58aa997c58c8

Tx prefix hash: 947998c4b22663c17152738618cef463aa3f129e1353a96295f17eed556ae68b
Tx public key: c74449a0f4fa22d5418e59f45ea412ce7b50de3c9828b82f0e383951bf231ffc
Timestamp: 1721350742 Timestamp [UCT]: 2024-07-19 00:59:02 Age [y:d:h:m:s]: 00:306:23:04:40
Block: 1068760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219336 RingCT/type: yes/0
Extra: 01c74449a0f4fa22d5418e59f45ea412ce7b50de3c9828b82f0e383951bf231ffc02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd432364e4ff3f57ef04014e3669632ae95327650d8ca88d13747a6b76e19bbe 0.600000000000 1539917 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": 1068770, "vin": [ { "gen": { "height": 1068760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd432364e4ff3f57ef04014e3669632ae95327650d8ca88d13747a6b76e19bbe" } } ], "extra": [ 1, 199, 68, 73, 160, 244, 250, 34, 213, 65, 142, 89, 244, 94, 164, 18, 206, 123, 80, 222, 60, 152, 40, 184, 47, 14, 56, 57, 81, 191, 35, 31, 252, 2, 17, 0, 0, 0, 2, 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