Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c95d0a24192dac69d4dcdc7b95a59b1a4a06d3e630ed048d4590acc4c2c1a67e

Tx prefix hash: 29507ae09be14a5e0991b9cf1323d5da665a6962f5dffe69fa70108947ace537
Tx public key: e9a9565429d6d15523adfc7a09dbe87963ca7d31dd5693a1c306cc618c01437e
Timestamp: 1715462406 Timestamp [UCT]: 2024-05-11 21:20:06 Age [y:d:h:m:s]: 01:181:00:15:11
Block: 1019967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387952 RingCT/type: yes/0
Extra: 01e9a9565429d6d15523adfc7a09dbe87963ca7d31dd5693a1c306cc618c01437e02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923cf3e4d07788bed5027c0185be290bd39f192ea9e1059728f58f902b483f06 0.600000000000 1484024 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": 1019977, "vin": [ { "gen": { "height": 1019967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923cf3e4d07788bed5027c0185be290bd39f192ea9e1059728f58f902b483f06" } } ], "extra": [ 1, 233, 169, 86, 84, 41, 214, 209, 85, 35, 173, 252, 122, 9, 219, 232, 121, 99, 202, 125, 49, 221, 86, 147, 161, 195, 6, 204, 97, 140, 1, 67, 126, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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