Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83a32bf0f0d1e53bb13f790ef8e4672ced2bdda1781259b05711b41f1bd55c15

Tx prefix hash: ae0983b7a14a684dc965ef211cdb69217f30e7f4f180b1b214116d056fe9ce7e
Tx public key: ada9cff3a0031db323985d529cc44a3558e1ff8b1b7ba2014e3f3078e2544db4
Timestamp: 1706619182 Timestamp [UCT]: 2024-01-30 12:53:02 Age [y:d:h:m:s]: 01:097:06:01:25
Block: 946597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330609 RingCT/type: yes/0
Extra: 01ada9cff3a0031db323985d529cc44a3558e1ff8b1b7ba2014e3f3078e2544db40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa518ca753d615a3ee56ad9b26e6b0e8d06d407aa04a38de995cbb63df14006a 0.600000000000 1404929 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": 946607, "vin": [ { "gen": { "height": 946597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa518ca753d615a3ee56ad9b26e6b0e8d06d407aa04a38de995cbb63df14006a" } } ], "extra": [ 1, 173, 169, 207, 243, 160, 3, 29, 179, 35, 152, 93, 82, 156, 196, 74, 53, 88, 225, 255, 139, 27, 123, 162, 1, 78, 63, 48, 120, 226, 84, 77, 180, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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