Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c02570e4524173f334aa7c322757845fe27f6e16efa8a6f9302bef4cfc5d8f64

Tx prefix hash: 97ac62a769b8cf63819b044e0f0dc4c9b7709d2bac602e26e1f59638587deb0e
Tx public key: 09d3f6e22a37c7a5978e6521180118d6ebe518e7f9aa386f566140cd7167ca59
Timestamp: 1723290219 Timestamp [UCT]: 2024-08-10 11:43:39 Age [y:d:h:m:s]: 00:220:23:10:08
Block: 1084840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157818 RingCT/type: yes/0
Extra: 0109d3f6e22a37c7a5978e6521180118d6ebe518e7f9aa386f566140cd7167ca59021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb80706af9328631f1cc1e7bb433fd18e709988885eb4786e8d1df796247005c 0.600000000000 1559259 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": 1084850, "vin": [ { "gen": { "height": 1084840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb80706af9328631f1cc1e7bb433fd18e709988885eb4786e8d1df796247005c" } } ], "extra": [ 1, 9, 211, 246, 226, 42, 55, 199, 165, 151, 142, 101, 33, 24, 1, 24, 214, 235, 229, 24, 231, 249, 170, 56, 111, 86, 97, 64, 205, 113, 103, 202, 89, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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