Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96cfdc9c53b753c3bd00ae7c731bc3ee5cc7f8a1d37766ef13ab8cde81f9fe5

Tx prefix hash: 4a70015cae080a42433c7038133e828faeec3a21fdd5d238754a730fe69b694b
Tx public key: a1e90c68e47d11d228101c258bd754c83633ea3b6dd5912c1838b7535c98f9ac
Timestamp: 1703170288 Timestamp [UCT]: 2023-12-21 14:51:28 Age [y:d:h:m:s]: 01:105:01:55:50
Block: 918026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336228 RingCT/type: yes/0
Extra: 01a1e90c68e47d11d228101c258bd754c83633ea3b6dd5912c1838b7535c98f9ac021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee48308bdb1b05bf9485a4cd4a75db59fbca7b5d47e3dab48620fead8d241fc1 0.600000000000 1375662 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": 918036, "vin": [ { "gen": { "height": 918026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee48308bdb1b05bf9485a4cd4a75db59fbca7b5d47e3dab48620fead8d241fc1" } } ], "extra": [ 1, 161, 233, 12, 104, 228, 125, 17, 210, 40, 16, 28, 37, 139, 215, 84, 200, 54, 51, 234, 59, 109, 213, 145, 44, 24, 56, 183, 83, 92, 152, 249, 172, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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