Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05f28c42752de86a78b5c83a74a599ee532b19846cb93b69391759ffbf29eaa

Tx prefix hash: 43079773851bc299220d6389f1ab6747d69ef8c3a7a9311e3b8260dc152e84e6
Tx public key: 84062f995298a3b1b2a6daf188aea59de6aa5abc6d37500c7599a60350c81936
Timestamp: 1710352802 Timestamp [UCT]: 2024-03-13 18:00:02 Age [y:d:h:m:s]: 01:011:22:07:59
Block: 977590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269487 RingCT/type: yes/0
Extra: 0184062f995298a3b1b2a6daf188aea59de6aa5abc6d37500c7599a60350c8193602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7307ded9d59f92179cc164c5a6c3cc027d04561d7ae6d61b106dc0db56b7ffc5 0.600000000000 1437593 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": 977600, "vin": [ { "gen": { "height": 977590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7307ded9d59f92179cc164c5a6c3cc027d04561d7ae6d61b106dc0db56b7ffc5" } } ], "extra": [ 1, 132, 6, 47, 153, 82, 152, 163, 177, 178, 166, 218, 241, 136, 174, 165, 157, 230, 170, 90, 188, 109, 55, 80, 12, 117, 153, 166, 3, 80, 200, 25, 54, 2, 17, 0, 0, 0, 5, 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