Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d98294cb5bf2ff7cd65155be252de65caadbcc6198768c62665c0968255e81

Tx prefix hash: e844f72518f209c97efec2f45f06546568aa4b69be02bc56d2b4aafa3e84be0a
Tx public key: 3236c429b62a8235d3e9bfea20cc5eb6eddce91c5cc4f7f5c369611a013be006
Timestamp: 1716145934 Timestamp [UCT]: 2024-05-19 19:12:14 Age [y:d:h:m:s]: 00:362:07:17:09
Block: 1025601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258983 RingCT/type: yes/0
Extra: 013236c429b62a8235d3e9bfea20cc5eb6eddce91c5cc4f7f5c369611a013be00602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b72604efb4537fab17581f268ff3c8e8e8e29d4f0fc333a6643b184cb8a93ae 0.600000000000 1492226 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": 1025611, "vin": [ { "gen": { "height": 1025601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b72604efb4537fab17581f268ff3c8e8e8e29d4f0fc333a6643b184cb8a93ae" } } ], "extra": [ 1, 50, 54, 196, 41, 182, 42, 130, 53, 211, 233, 191, 234, 32, 204, 94, 182, 237, 220, 233, 28, 92, 196, 247, 245, 195, 105, 97, 26, 1, 59, 224, 6, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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