Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97767f97a349ae4fc87bc413d893b9f04e669b223e3583f737fb7d71374dbd1

Tx prefix hash: d6985ee2f64235c2676d802e1a9cefd84a7b2a3c811eba507e3a9ae56389e80a
Tx public key: afe7b893f4c038874d57a9dc01f3030c7d2d7a5708e8e841e72e32bdfa0a6b22
Timestamp: 1730073739 Timestamp [UCT]: 2024-10-28 00:02:19 Age [y:d:h:m:s]: 00:080:17:14:04
Block: 1141012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57730 RingCT/type: yes/0
Extra: 01afe7b893f4c038874d57a9dc01f3030c7d2d7a5708e8e841e72e32bdfa0a6b220211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66e8a5382f2bb427c98b240274fc6bd743d88404098101b05f73295e76ac2251 0.600000000000 1624819 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": 1141022, "vin": [ { "gen": { "height": 1141012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66e8a5382f2bb427c98b240274fc6bd743d88404098101b05f73295e76ac2251" } } ], "extra": [ 1, 175, 231, 184, 147, 244, 192, 56, 135, 77, 87, 169, 220, 1, 243, 3, 12, 125, 45, 122, 87, 8, 232, 232, 65, 231, 46, 50, 189, 250, 10, 107, 34, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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