Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d520ea0a8eb3a13e822ed27e8d2f58bdc947c6d17d68b76ef993f4982a21ffe

Tx prefix hash: e24062ce895b6d634496c60b1750302830ced87992fdf4d24cfc80dd513f32ca
Tx public key: 4ef3481672aebcc2f7fc28fb45c1631d129d25d4a6c3d5ec88ee2cfc28be0aa6
Timestamp: 1729888797 Timestamp [UCT]: 2024-10-25 20:39:57 Age [y:d:h:m:s]: 00:029:08:02:34
Block: 1139501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20952 RingCT/type: yes/0
Extra: 014ef3481672aebcc2f7fc28fb45c1631d129d25d4a6c3d5ec88ee2cfc28be0aa6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 977849ca58805845f49d66274bc6e263ca94b2a92741f3ef10e0ae83838cc7cd 0.600000000000 1623288 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": 1139511, "vin": [ { "gen": { "height": 1139501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "977849ca58805845f49d66274bc6e263ca94b2a92741f3ef10e0ae83838cc7cd" } } ], "extra": [ 1, 78, 243, 72, 22, 114, 174, 188, 194, 247, 252, 40, 251, 69, 193, 99, 29, 18, 157, 37, 212, 166, 195, 213, 236, 136, 238, 44, 252, 40, 190, 10, 166, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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