Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93859cf2bb5b4a798889c49680d400952df158e70b2978e0b98bb0afd1157122

Tx prefix hash: 0a96dc0b909aa299ecc7f282424206148a6a65328eda28d56f07e9dfc3164bf0
Tx public key: f6c9c0ac37916ba89bf23db7f0e0effcd3d44d699a64f40d45b2fb453e0328e8
Timestamp: 1700942405 Timestamp [UCT]: 2023-11-25 20:00:05 Age [y:d:h:m:s]: 01:055:07:02:55
Block: 899557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300873 RingCT/type: yes/0
Extra: 01f6c9c0ac37916ba89bf23db7f0e0effcd3d44d699a64f40d45b2fb453e0328e8021100000001e08532b6000000000000000000

1 output(s) for total of 0.641791882000 dcy

stealth address amount amount idx
00: 169170b35e4e8019137af01c397a01da04947064a43c9746fe9b5d393be6aec7 0.641791882000 1356016 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": 899567, "vin": [ { "gen": { "height": 899557 } } ], "vout": [ { "amount": 641791882, "target": { "key": "169170b35e4e8019137af01c397a01da04947064a43c9746fe9b5d393be6aec7" } } ], "extra": [ 1, 246, 201, 192, 172, 55, 145, 107, 168, 155, 242, 61, 183, 240, 224, 239, 252, 211, 212, 77, 105, 154, 100, 244, 13, 69, 178, 251, 69, 62, 3, 40, 232, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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