Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3cb58fc8f56a6fce49ec6ae3fb82e91cf924406679628529ecc76ae6e459b55

Tx prefix hash: ed0993ce0e2a294d03d378cc4c4aa6218811b44fcebb1015a15f4180d1159f78
Tx public key: 2fa83e9c411551b841f37a82c4919761657fd9b2b945dd0efae9ac53ef8fa812
Timestamp: 1685087506 Timestamp [UCT]: 2023-05-26 07:51:46 Age [y:d:h:m:s]: 02:004:19:39:22
Block: 768361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525564 RingCT/type: yes/0
Extra: 012fa83e9c411551b841f37a82c4919761657fd9b2b945dd0efae9ac53ef8fa812021100000001b3164c24000000000000000000

1 output(s) for total of 1.746229101000 dcy

stealth address amount amount idx
00: 0a11d61f0d97ce46583dccc4d7a640f534bc7e9ed86beafd16981e739c7119af 1.746229101000 1217556 of 0

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": 768371, "vin": [ { "gen": { "height": 768361 } } ], "vout": [ { "amount": 1746229101, "target": { "key": "0a11d61f0d97ce46583dccc4d7a640f534bc7e9ed86beafd16981e739c7119af" } } ], "extra": [ 1, 47, 168, 62, 156, 65, 21, 81, 184, 65, 243, 122, 130, 196, 145, 151, 97, 101, 127, 217, 178, 185, 69, 221, 14, 250, 233, 172, 83, 239, 143, 168, 18, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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