Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc5d666d5d6a3e8104797957483e337244f7b533020c173f71f54e90eaed60b

Tx prefix hash: 680bd67ad5dbd80f0d73bbdf11c25e7db38e13a0aa6a1899651951155a312ac8
Tx public key: a73e42792edaa785b30fb363214bea95dca5d9b480c429b4eda550cd6aa7e8c8
Timestamp: 1674371280 Timestamp [UCT]: 2023-01-22 07:08:00 Age [y:d:h:m:s]: 02:124:04:13:22
Block: 680144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610436 RingCT/type: yes/0
Extra: 01a73e42792edaa785b30fb363214bea95dca5d9b480c429b4eda550cd6aa7e8c80211000000025029cbac000000000000000000

1 output(s) for total of 3.422949794000 dcy

stealth address amount amount idx
00: f1b0b541aed08bf4b4e879b984a361ddaf263323a0422089ad3ea791397083e7 3.422949794000 1122171 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": 680154, "vin": [ { "gen": { "height": 680144 } } ], "vout": [ { "amount": 3422949794, "target": { "key": "f1b0b541aed08bf4b4e879b984a361ddaf263323a0422089ad3ea791397083e7" } } ], "extra": [ 1, 167, 62, 66, 121, 46, 218, 167, 133, 179, 15, 179, 99, 33, 75, 234, 149, 220, 165, 217, 180, 128, 196, 41, 180, 237, 165, 80, 205, 106, 167, 232, 200, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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