Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bebf884a318fee16e0028af64c65bcf1e89cc280946e7df46eebb2556451de65

Tx prefix hash: 006b5b1dafd24c9259ec3ff1ea61c581d359c8acf2ccc6b733304c7d73b81c4e
Tx public key: e7efd0ecae06f451873056d85813d8201fb6b3ee4e05be8af7d1e113fe83522a
Timestamp: 1706226677 Timestamp [UCT]: 2024-01-25 23:51:17 Age [y:d:h:m:s]: 01:031:04:49:12
Block: 943340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283357 RingCT/type: yes/0
Extra: 01e7efd0ecae06f451873056d85813d8201fb6b3ee4e05be8af7d1e113fe83522a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8780d91890c7d5c0dfda1540c57649bbb18895a14f1ba4f11357a9dbc965b53d 0.600000000000 1401546 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": 943350, "vin": [ { "gen": { "height": 943340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8780d91890c7d5c0dfda1540c57649bbb18895a14f1ba4f11357a9dbc965b53d" } } ], "extra": [ 1, 231, 239, 208, 236, 174, 6, 244, 81, 135, 48, 86, 216, 88, 19, 216, 32, 31, 182, 179, 238, 78, 5, 190, 138, 247, 209, 225, 19, 254, 131, 82, 42, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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