Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f0075a2e6c043e3066ef350be62bf293575db7808a93eaeb05c47f031a3d83

Tx prefix hash: 5cdb108bd90f8ae4d3a5c1b1da96407f5ea3a1d84fad4a8490001468399121d1
Tx public key: 13dd25325e3b43ac10c8f5de10e70947a3665240d04397c02b7a97c8ac79bf4d
Timestamp: 1579549148 Timestamp [UCT]: 2020-01-20 19:39:08 Age [y:d:h:m:s]: 05:013:16:21:03
Block: 49596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160169 RingCT/type: yes/0
Extra: 0113dd25325e3b43ac10c8f5de10e70947a3665240d04397c02b7a97c8ac79bf4d0211000000098a2ee0d9000000000000000000

1 output(s) for total of 420.405798341000 dcy

stealth address amount amount idx
00: ceafc3e4f9f6c4c00adba88c6ecd7d7d6e7274d730de6d0ae41e3e6c2dcfa67d 420.405798341000 92142 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": 49606, "vin": [ { "gen": { "height": 49596 } } ], "vout": [ { "amount": 420405798341, "target": { "key": "ceafc3e4f9f6c4c00adba88c6ecd7d7d6e7274d730de6d0ae41e3e6c2dcfa67d" } } ], "extra": [ 1, 19, 221, 37, 50, 94, 59, 67, 172, 16, 200, 245, 222, 16, 231, 9, 71, 163, 102, 82, 64, 208, 67, 151, 192, 43, 122, 151, 200, 172, 121, 191, 77, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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