Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f638e8fe878c1d85058d1a602c9703aaba813867a6b9c05e2564a34b663a73c5

Tx prefix hash: 123a7789d5314e77e6ae8655730e16d397064e76f3dca35b125325e313097152
Tx public key: 2fe1d24a91c23b522cb82254aa6102a559818e33a53ab8f066f63350dd31be92
Timestamp: 1704638625 Timestamp [UCT]: 2024-01-07 14:43:45 Age [y:d:h:m:s]: 01:119:16:47:26
Block: 930178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346684 RingCT/type: yes/0
Extra: 012fe1d24a91c23b522cb82254aa6102a559818e33a53ab8f066f63350dd31be920211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 496d6ebe88db288dc6636e5d0920b34055f8344268a1149c2e94f6872d7c0da1 0.600000000000 1388060 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": 930188, "vin": [ { "gen": { "height": 930178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "496d6ebe88db288dc6636e5d0920b34055f8344268a1149c2e94f6872d7c0da1" } } ], "extra": [ 1, 47, 225, 210, 74, 145, 194, 59, 82, 44, 184, 34, 84, 170, 97, 2, 165, 89, 129, 142, 51, 165, 58, 184, 240, 102, 246, 51, 80, 221, 49, 190, 146, 2, 17, 0, 0, 0, 3, 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