Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fce3290fda764043cc13cb7f2e7d746135d5e26f411fe291bf455198608052b

Tx prefix hash: f53eea516b73ed9ff68c93ccb5631f83ce58789423a00883ad5951a71caa16e3
Tx public key: d214047584d27ba33b1500803be3244f9f0b7ee8c103244f308c5592cdfd245b
Timestamp: 1722809755 Timestamp [UCT]: 2024-08-04 22:15:55 Age [y:d:h:m:s]: 00:171:06:43:31
Block: 1080844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122499 RingCT/type: yes/0
Extra: 01d214047584d27ba33b1500803be3244f9f0b7ee8c103244f308c5592cdfd245b021100000006e914dd15000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: a667f41f3a61214302a14dc42a9c5cc4f2cf2110c79682c7fba84f6489dd5b17 0.615590000000 1554359 of 0

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": 1080854, "vin": [ { "gen": { "height": 1080844 } } ], "vout": [ { "amount": 615590000, "target": { "key": "a667f41f3a61214302a14dc42a9c5cc4f2cf2110c79682c7fba84f6489dd5b17" } } ], "extra": [ 1, 210, 20, 4, 117, 132, 210, 123, 163, 59, 21, 0, 128, 59, 227, 36, 79, 159, 11, 126, 232, 193, 3, 36, 79, 48, 140, 85, 146, 205, 253, 36, 91, 2, 17, 0, 0, 0, 6, 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