Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669fb553b3ca45d1d4eb7240e73fe323f0ca9161268f2f13f977fc127483c7bc

Tx prefix hash: 4a32a84942a14bf61533a44fb2bd2190cc7e3bf9f01b6e26b5f431cba17f8553
Tx public key: 418922f51792f64219725de3f0c62d0c5abfd13dddcc51d8611596a7f0eb74b6
Timestamp: 1724481714 Timestamp [UCT]: 2024-08-24 06:41:54 Age [y:d:h:m:s]: 01:071:20:19:23
Block: 1094720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309782 RingCT/type: yes/0
Extra: 01418922f51792f64219725de3f0c62d0c5abfd13dddcc51d8611596a7f0eb74b6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b4bb971ca9bd23b8dde65999d4978f6b06cdc489ded5985d47d6e9e908c158f 0.600000000000 1569839 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": 1094730, "vin": [ { "gen": { "height": 1094720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b4bb971ca9bd23b8dde65999d4978f6b06cdc489ded5985d47d6e9e908c158f" } } ], "extra": [ 1, 65, 137, 34, 245, 23, 146, 246, 66, 25, 114, 93, 227, 240, 198, 45, 12, 90, 191, 209, 61, 221, 204, 81, 216, 97, 21, 150, 167, 240, 235, 116, 182, 2, 17, 0, 0, 0, 7, 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