Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a866936b0084943d5c466fcc8a39306cc8a6348b0fa5929bd53405198784abb5

Tx prefix hash: d4bd7a205d65c4f642c193e3fcc53e05917a4af2453ada87f8257603f1c8a21d
Tx public key: 1e833a881a9d5ceccf913571abb27e69f22e85f48dc4bba6950ab1b8a606f58b
Timestamp: 1722092791 Timestamp [UCT]: 2024-07-27 15:06:31 Age [y:d:h:m:s]: 00:247:04:56:51
Block: 1074905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176584 RingCT/type: yes/0
Extra: 011e833a881a9d5ceccf913571abb27e69f22e85f48dc4bba6950ab1b8a606f58b021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcc8421b865947e541f2a9e569ee549c679df03496bdd536e0d0c57875d731fc 0.600000000000 1547424 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": 1074915, "vin": [ { "gen": { "height": 1074905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcc8421b865947e541f2a9e569ee549c679df03496bdd536e0d0c57875d731fc" } } ], "extra": [ 1, 30, 131, 58, 136, 26, 157, 92, 236, 207, 145, 53, 113, 171, 178, 126, 105, 242, 46, 133, 244, 141, 196, 187, 166, 149, 10, 177, 184, 166, 6, 245, 139, 2, 17, 0, 0, 0, 8, 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