Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02bfe49fb51c1a928669b222ec855dd83a9ceedc82dd6a20109d948fc26ec2a7

Tx prefix hash: bbe09e78ec5ddfae32c6a6ac0851c8daf103124d279c1aadb055f20e3e8bbbeb
Tx public key: 35e06eccc0f364872be9f911bbf0219b8996a29ed4b1d4be818d590bf6ccc5e8
Timestamp: 1727530822 Timestamp [UCT]: 2024-09-28 13:40:22 Age [y:d:h:m:s]: 00:168:21:25:35
Block: 1120000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120511 RingCT/type: yes/0
Extra: 0135e06eccc0f364872be9f911bbf0219b8996a29ed4b1d4be818d590bf6ccc5e802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 108a8b037ef938582c8fcd1028ae64a2355150c8df86c4c9273f165295242ea8 0.600000000000 1601761 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": 1120010, "vin": [ { "gen": { "height": 1120000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "108a8b037ef938582c8fcd1028ae64a2355150c8df86c4c9273f165295242ea8" } } ], "extra": [ 1, 53, 224, 110, 204, 192, 243, 100, 135, 43, 233, 249, 17, 187, 240, 33, 155, 137, 150, 162, 158, 212, 177, 212, 190, 129, 141, 89, 11, 246, 204, 197, 232, 2, 17, 0, 0, 0, 7, 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