Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342df8fdbb894650dc521c4a6f33bd0a6f397de445c5a0ca801a969978f4967b

Tx prefix hash: 99cb65f697f0931566431c94653c0f0fb7877efc10532a93c6b85fe7aedd47ab
Tx public key: 9b68ff4716fac1271a0c36c793aa522060686e69f7aa500531bfbad75c7aabc3
Timestamp: 1729371965 Timestamp [UCT]: 2024-10-19 21:06:05 Age [y:d:h:m:s]: 00:178:08:20:37
Block: 1135255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127241 RingCT/type: yes/0
Extra: 019b68ff4716fac1271a0c36c793aa522060686e69f7aa500531bfbad75c7aabc3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4641ee9dd4cab3e1ec20def4ce24012d7fac14afcdfde7baf5ed974e7e1d3e8a 0.600000000000 1618586 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": 1135265, "vin": [ { "gen": { "height": 1135255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4641ee9dd4cab3e1ec20def4ce24012d7fac14afcdfde7baf5ed974e7e1d3e8a" } } ], "extra": [ 1, 155, 104, 255, 71, 22, 250, 193, 39, 26, 12, 54, 199, 147, 170, 82, 32, 96, 104, 110, 105, 247, 170, 80, 5, 49, 191, 186, 215, 92, 122, 171, 195, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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