Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 447d610a9027bff483145b37ebeb7e2881f8f57fc57b209038939e61ac2f8822

Tx prefix hash: db03f74e0348e8e419df0e1713ddd4b71998443f1a178c740f2eda3321fb8b85
Tx public key: 1bb5ab23d3b6cf3eadfa59dc9f4349593c27a0f2701fb88089348a81e799e374
Timestamp: 1709057443 Timestamp [UCT]: 2024-02-27 18:10:43 Age [y:d:h:m:s]: 01:094:03:05:23
Block: 966847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328323 RingCT/type: yes/0
Extra: 011bb5ab23d3b6cf3eadfa59dc9f4349593c27a0f2701fb88089348a81e799e3740211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee77a89e5f98ab908da4f8d06a994550ed84a4311bfc9d5f4fc0492c6dc751a4 0.600000000000 1426618 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": 966857, "vin": [ { "gen": { "height": 966847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee77a89e5f98ab908da4f8d06a994550ed84a4311bfc9d5f4fc0492c6dc751a4" } } ], "extra": [ 1, 27, 181, 171, 35, 211, 182, 207, 62, 173, 250, 89, 220, 159, 67, 73, 89, 60, 39, 160, 242, 112, 31, 184, 128, 137, 52, 138, 129, 231, 153, 227, 116, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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